Viewing run history and troubleshooting a workflow

When a contact doesn't get the message you expected, Run History shows you exactly what happened. It lists every run of the workflow, one per contact, and lets you open any run to see each step that executed and why it stopped.

Open Run History

Run History lives inside each workflow, alongside the Builder and Enrollments tabs.

1. Open the workflow

   Go to Workflows and select the workflow you want to inspect.

2. Switch to the Run History tab

   At the top right of the workflow, click Run History. You'll see the most recent runs, with a run count and a Refresh button.

3. Scan the run list

   Each row shows the contact's name, the trigger that enrolled them, a step summary like 4/6 steps, the duration, and how long ago they were enrolled. The status icon on the left tells you the outcome at a glance: completed, failed, cancelled, active, scheduled, or waiting. A run with any failed step is flagged in red.

4. Load older runs

   Reached the bottom? Click Load more to pull in earlier runs.

Read a step-by-step trace

Click any run to expand it. SAMI OS loads the full timeline of that run so you can follow it step by step.

• Step status — each step carries its own badge (completed, failed, scheduled, waiting, skipped, or cancelled) and its run time, so you can see where the contact got stuck or how long a delay step held them.
• Error messages — when a step fails, its error appears in red right under the step name. This is usually your first clue for a message that never sent.
• Input, Output, and Trace — expand these to see the data the step received, what it returned, and the underlying trace. Use them to confirm a contact had a valid phone number or email before a send step ran.
• Branch taken — for path and condition steps, a Branch → line shows which route the contact followed, so you can tell whether they went down the path you intended.
• Scheduled time — a step that's still waiting shows exactly when it's set to run next.

Fix what you find

Once you know the cause, you can act on it. A bad step configuration or a missing field usually means editing the workflow in the Builder and republishing. A messaging failure tied to your sending setup may point to phone or A2P registration settings. To re-run a contact, manage them from the Enrollments tab, then check Run History again after the next attempt. You can also open the contact directly from any run to review their full contact timeline.

Related articles

• Publishing and activating a workflow
• Managing who is enrolled in a workflow
• Managing, organizing, and deleting workflows