Runs: what a flow did, why it failed, and analytics
Every time a flow runs — its status, what each step received and returned, why a step failed, the flow's versions, running it again, and the Analytics page across all flows.
Every start of a flow is a run. Open a flow's runs from Flows → ⋯ → View Runs, or with the run-history button in the editor's toolbar.
The run list
Run History lists the runs, newest first, with their Trigger, Started, Steps, Status and Duration; it refreshes every few seconds. Run Now starts the published flow.
| Status | Means |
|---|---|
| QUEUED | About to start. |
| RUNNING | Running now. |
| SUCCESS | Every step finished. |
| FAILED | A step failed and the flow stopped there. |
| TIMEOUT | The run took too long and was stopped. |
| CANCELLED | Stopped on purpose — for example its flow was switched off during a wait, or the person ordered during a recipe's wait. |
| WAITING | In a Wait, with resumes in … — a recipe's series spends days like this, by design. |
| WAITING FOR THE AGENT | A Run agent step is waiting for its agent. |
| NEEDS APPROVAL | Waiting for a decision — only flows built with the approval step, which is no longer offered. |
A run's details
Click a run to open Run Details:
- Summary — Trigger, Duration, Steps Executed, Started.
- Trigger Data — exactly what started it.
- Each step — its input and output, how long it took, and the Error when it failed. A branch shows which way it went.
- AI steps — their output shows the cost and the rounds they used; the totals are on AI Usage: AI in Automation.
- Versions — the flow's published versions and what changed between them.
On a recipe's page in the Hub, Open Run Inspector ↗ comes here: A recipe's results.
Run it again
There is no retry of a single run from the step that failed. After fixing the cause, Run Now starts the flow again from the trigger. For a flow started by an event — an order, a webhook — the next event runs it; a manual run starts with no event data, so steps that read {{trigger.…}} get nothing.
Running again repeats every step for real: an e-mail step sends again.
Analytics
Analytics in the menu sums up all flows for 24h, 7d or 30d: Total Runs, Success Rate, In Progress, Avg Duration, Runs Over Time, and Top Flows with their runs, successes and failures.
If something doesn't work
Unresolved flow variable {{ … }} — the referenced upstream output is missing
A step used a value from a step that did not run or did not return it — often a step on the other arm of a branch, or a typo in the pill. Open the step's Input to see what it got.
Flow execution timeout
The run went past its time limit — usually a slow outside app. If it keeps happening, turn on Retry on failure for that step, or split the work into two flows.
The run failed with 401 or 403 from an app
The connection's key is no longer accepted. Reconnect it: Connections.