Every run of every workflow shows up two places: a workflow's own Runs tab, and the workspace-wide Runs page. Both use the same table — search by record, and filter by status or date.
Search by record looks across all your runs, not just the ones loaded on screen. It matches the start of the words in the record's name and in the recipient's name or email. Runs of AI workflows show their record too, with an Open link (such as Open lead or Open invoice) for the records the app can open. If nothing matches among the latest runs, choose Load older runs to keep looking.
Run statuses
- Delivered — the run finished and, if it messaged someone, the message sent.
- Failed — a step's action failed. Open the run to see the error.
- Skipped — the record didn't meet a filter, so no step ran, or a step had no one to send to (for example, the lead has no email address). The run says which. An incoming-message run can be skipped because the channel already has 10 incoming workflows on ("Not run: this channel already has 10 incoming workflows on") or because the email was automatic, such as an auto-reply or a mailing list.
- Stopped — a Stop the workflow step's condition matched, and the run ended there on purpose. The run names the rule that matched. A run is also stopped, at the step that would have changed the record, when workflows have changed the same record 3 times in 10 minutes (see loop protection).
- Waiting — a wait or a delayed step hasn't finished yet.
- Needs review — an AI decision wasn't confident enough and is waiting for you to choose Yes or No, retry the decision, or cancel the run.
- Test — from a Test run. Test runs never send anything for real, so a Test status is never a real send.
The counts at the top of the Runs page — Runs for the date range, Delivered, Failed, and Waiting — are counted on the server, not just from what's loaded on screen. The date filter switches between the last 7 and 30 days. Stopped runs count toward Runs; skipped and test runs don't, and a note under the counts says so.
Opening a run
Opening a run shows the same flow, read-only, with a mark on each step for its result. Click a step to see its Summary, Message, and Details. Summary shows the result, the recipient, or the error. For a Client stage changed run it also shows the move, for example "Stage: Lead → Onboarding", and who made it: a teammate, an automatic rule, or a workflow. Message appears only for steps that send one. Details shows an AI decision's answer, confidence, and reason, plus timestamps and IDs.
A run made from a published version says which one. If the workflow has moved on since, the run shows "This run used version 2. The workflow is on version 3." A step that didn't run on the chosen path shows Not on this path. A step that was moved by Wait until a date shows "Moved to" its new date, and one held for business hours shows "Held for business hours until" the time it will send. A Check a condition step shows its answer, Yes or No. A step that Waiting until a date shows that date.
Retrying a failed run
Retry from failed step re-runs just the step that failed and everything after it — earlier steps never run again. Only failed runs can be retried, and you need permission to edit workflows. The app refuses if the workflow is off, was deleted, or has changed since that run, or while a step from the run may still be sending; fix the cause first (for example, add the missing email address to the lead), then retry. You'll find it in a run's row menu and on the run itself.
How long runs are kept
Run history is kept for 90 days after the run's last step. A run that waits a long time, up to 365 days, keeps its history until 90 days after its last step finishes. When you delete a workflow, its run history is kept for 90 days too.
Exporting
Export CSV downloads the runs you're looking at as a CSV file, with a Run, Status, Record, Started, Duration, and Error column for each run. On the workspace Runs page there's also a Workflow column.
Next steps
Return to Workflows for the list and how to start one.