The Runs tab gives you a real-time view of every contact’s journey through a workflow. Use it to verify that contacts are progressing as expected, diagnose errors, and inspect timing at the node level. You can access the Runs tab from the top of any workflow, alongside the Editor and Emails tabs.
Layout
The Runs view is split into two panels:
- Left panel. A scrollable list of every contact who has entered the workflow. Each entry displays the contact’s name or email address and the elapsed time since they entered. A search bar at the top lets you find a specific contact by name or email.
- Right panel. A visual map of the workflow showing the selected contact’s path through each node, with status badges indicating how far they have progressed.
Filtering runs
A dropdown next to the search bar lets you filter the contact list by run status:
| Filter | Description |
|---|
| All runs | Every contact who has entered the workflow, regardless of current state. |
| Running | Contacts currently progressing through nodes. They have not yet reached an exit or the end of the workflow. |
| Completed | Contacts who have finished the workflow by reaching an Exit condition or the final node in the sequence. |
| With errors | Contacts whose run includes at least one node action that failed. Use this filter to quickly surface problems. |
Aggregate statistics
Four metrics are displayed at the bottom of the left panel, summarizing the overall health of the workflow:
| Metric | Description |
|---|
| Completed | Total number of contacts who have finished the workflow. |
| Errored actions | Total number of individual node executions that failed across all runs. A single contact’s run can contribute multiple errored actions if more than one node failed. |
| In progress | Number of contacts currently inside the workflow. This matches the contact count shown in the top-right corner of the workflow header (next to the Active/Paused badge). |
| Avg. duration | Mean time from when a contact entered the workflow to when they exited. Only completed runs are included in this calculation. |
Inspecting an individual run
Select a contact in the left panel to load their run in the right panel. The workflow map highlights the contact’s specific path, and each node they have encountered displays a status badge:
| Badge | Meaning |
|---|
| Success: green checkmark | The node executed successfully and the contact has moved past it. |
| **Running: **green/teal spinner | The node is currently executing or the contact is waiting inside it (e.g. a Time Delay or Wait For node). |
| Greyed out: no badge | The contact has not reached this node yet. |
Node timing detail
Click any node within a contact’s run to open a detail overlay showing:
- Entered. The exact date and time the contact arrived at this node
- Exited. The exact date and time the contact left this node. If the contact is still inside the node (status is Running), this field is not displayed.
These timestamps are useful for verifying that delay nodes are holding contacts for the expected duration, confirming that action nodes executed promptly, and diagnosing bottlenecks where contacts are spending more time than expected.
Interaction with paused workflows
When a workflow is paused, all in-progress runs freeze in place. The Runs tab continues to display these contacts, but their status badges and timers will not update until the workflow is resumed. Contacts inside delay nodes (Time Delay, Wait For, Wait Until Condition Met) have their timers suspended. The countdown does not continue while the workflow is paused. 
