Relay

Docs navigation

Monitoring runs

Every flow has its own Runs page — click Runs in the flow builder's header, next to the run count. It shows the 50 most recent times this flow ran, most recent first.

  1. Open the flow from the Flows list, then click Runs in the header (the button also shows the flow's total run count).

  2. Each row shows: the contact, a status badge, the node the run is currently at (or ended at), when it started, how many re-prompts it used, and how long it ran for.

    The Runs page for a flow, one row expanded to show captured variables and its status badge highlightedThe Runs page for a flow, one row expanded to show captured variables and its status badge highlighted
    Row 1: the status badge. Row 2: the current or final node.

  3. Click a row to expand it. This reveals two things: any variables a Collect input node captured during that run, and the full event log — a timestamped, step-by-step account of everything the engine did (message sent, reply received, node advanced, handoff triggered, and so on).

    An expanded run row showing captured variables and a timestamped event log ending in a handoff eventAn expanded run row showing captured variables and a timestamped event log ending in a handoff event
    The event log is the fastest way to see exactly where a specific contact's run stopped and why.

If a flow has never run, the page explains that — trigger it from a personal WhatsApp number (by typing its keyword, or by being a contact's first-ever message, depending on the trigger type) to see a run appear here.

Reading captured variables

For flows with a Collect input chain, the expanded row lists every variable saved so far, with the value the contact actually sent — this is the quickest way to check what a specific person answered without digging through the raw conversation.

When to use this page vs. the shared inbox

The Runs page tells you what the flow did — which node it's at, whether it's waiting, why it stopped. The shared inbox tells you what the conversation looks like to the contact. For a stuck or confusing conversation, start on the Runs page to see the current node and event log, then open the conversation in the inbox if you need to see the actual message thread or reply yourself.