Every automation run is recorded. This lesson shows where that history lives — the Last 7 days summary and the Run history tab on the Automations page — and how to use it to sort out a run that stopped.
Before you start
- Manager access or above ('manage automations')
- At least one automation that has run
Two places on the Automations page
The Automations tab carries a Last 7 days summary — runs done, stopped and waiting — and each rule's row shows its last run. The Run history tab lists every run, a page at a time, with its automation, what started it, when, how long it took and its result.
One run, step by step
Click a run in Run history to open it in a drawer: what happened at each step, in order. A step that was skipped says its conditions weren't met; a step that stopped says why. A run waiting on someone shows as Needs you.
Sorting out a stopped run
When a run stops, the drawer shows which step stopped and the reason — a missing field, a permission problem, or an unreachable service. Fix the cause, then retry the step, or skip it and let the run carry on. To see how a rule behaves without waiting for a real event, use Test in the editor.
-
1
Scan the summary
On Settings › Automations, Last 7 days gives an at-a-glance health check, and each rule's last run sits in its row. Use it to spot a rule that keeps stopping, or whose steps are skipped more often than expected.
-
2
Open a run in Run history
Open the Run history tab (or ⋯ › Run history in a rule's editor for that rule's runs). Filter by automation, result or time, then click a run to see each step's result; a stopped step can be retried or skipped from there.
Tips & pitfalls
- A skipped step is not an error — it means the rule ran but that step's conditions weren't met, so it was intentionally not performed.
- Test in the editor runs the rule against a matter you choose without sending or changing anything, so you can check a rule before it runs for real.
Key takeaways
- The Automations tab shows a Last 7 days summary and each rule's last run
- Run history lists every run; a run opens in a drawer with each step's result
- A stopped step can be retried or skipped once the cause is fixed
Put the lesson into practice.
Book a guided session and our team will help you configure MatterFirst for your own practice.
We can't find the internet Attempting to reconnect
Something went wrong! Attempting to reconnect