View run history
The run history tab has two sections: a performance graph at the top and a table of individual runs below.
Performance graph
The graph shows successful and failed runs over time. Toggle between three time periods:- 24h — the last 24 hours
- 7 days — the last week
- 30 days — the last month
- Total — total number of runs in the period
- Success — number of successful runs
- Error rate — percentage of runs that failed
- Avg duration — average time to complete a run
Run table
The table lists each individual run with the following columns:- Status — whether the run is active, finished (successful), failed, or waiting
- Triggered at — when the run started
- Triggered for — the record that triggered the automation
- Duration — how long the run took to complete
- Actions performed — how many actions ran
Sort runs
Click the column headers to sort by Status or Triggered at. Runs are sorted by most recent by default.View run details
Click View actions
Click View actions on the run you want to inspect. A panel opens showing each action that ran.
Stop a running automation
If an automation is currently running and you need to stop it:Find the active run
Open the automation’s Run history tab and locate the run with an Active or Waiting status.
Activity chart on the list page
The automations list page shows an aggregate activity chart across all your automations. This chart displays the last 30 days of runs, with green bars for successful runs and red bars for failures. Each automation row also shows:- Status — the result of the most recent run and when it happened
- Total runs — total runs in the last 7 days
- Success rate — percentage of successful runs in the last 7 days
FAQ
Can I retry a failed run?
Can I retry a failed run?
Yes. Failed runs can be retried within 24 hours. The retry picks up from the last failed action.
How long is run history kept?
How long is run history kept?
Run history is kept indefinitely. You can delete all run history from the automation’s Settings tab under Danger zone.
Why does a run show as 'waiting'?
Why does a run show as 'waiting'?
A run shows as waiting when it has reached a Wait action and is paused for the configured duration. It will resume automatically.