Each time an automation starts for a client, it makes a run. Run history lists them, newest first, and each run shows what happened step by step.
Steps
- Open the automation from Automations.
- Open the ⋮ menu (More actions) and click Run history.
- Use the filters to show All, Running, Completed, Stopped or Failed runs, or Skipped to see clients the trigger matched but no run started for.
- Click a client’s name to open the run. Each step shows whether it ran, was skipped, is held, is waiting, or failed, with the reason.
Good to know
- The Automations list puts a live automation with failed runs in the last 7 days, or one that paused itself, at the top with Review runs.
- A step that is held is waiting out quiet hours or the daily message limit.
- A failing step is retried a few times before the run gives up and shows Failed, including when the step’s last try never finished.
- A Stopped run says why, such as The client no longer matched the conditions, The automation was paused before this step, All automations were paused, Automations were paused for this client, What started the run no longer applies, such as a cancelled visit, The client was archived, or a Stop early when goal it met, such as Goal met: they replied to an email. The step it stopped at says what happened, such as “Sam replied on Tue, Oct 14”.
- Each run shows the version it ran on, so you can tell runs before and after a change apart.
- Skipped lists each client with why the automation last passed them over: not at the automation’s locations, an Only if condition they didn’t meet (named, such as Didn’t match Only if: Client type), it already ran for them once, it was still running for them, they already met one of its Stop early when goals (such as Already met one of its goals: already a client), or automations were paused for your team or the client. Each client shows only their latest skip. Visits for another service, or other events the trigger isn’t set for, aren’t skips.
Troubleshooting
- A client didn’t get a message. Open their run. A skipped message step names the channel and why, such as no email on file, The client unsubscribed from automated emails, no agreement to texts, or the client is marked Do not contact.
- There’s no run for a client. Choose Skipped to see whether they matched the trigger but didn’t start, and why. If they aren’t there, check they matched the trigger’s own settings, such as the service or status, and that the automation was live at the time. A Test run shows who would have started and why others didn’t.
Related
Last updated