Reading the run log
What an automation did, when it did it, and why it failed when it failed.
Each automation's row on Workspace → Automations shows how many times it has run and when it last ran. View runs opens its 20 most recent runs, newest first.
What counts as a run
A run is recorded each time the event happened and every condition held - each time the automation actually acted. An event whose conditions did not match leaves nothing behind, so a rule that never matches shows no runs at all.
OK and Failed
A run is OK when every action succeeded. It is Failed when at least one did not, and its message is the first failure's reason. The other actions on that run still ran.
Common failures
- Webhook URL was blocked - the address resolves to a private or internal network. A webhook can reach only public addresses, over http or https.
- Webhook responded with HTTP … - the receiving system refused or failed. A webhook waits five seconds at most, does not follow redirects and is not retried.
- Needs add-ons this workspace no longer has - a payment-link action whose add-on has since been switched off.
A rule on an event from a module you have since switched off stops running altogether. It leaves no failed runs, because it no longer runs.