The Runs tab lists every execution, newest first, with its status and duration.
The Runs list
Open Automations and switch to the Runs tab. Each row shows:
Narrow the list with the flow dropdown (All flows) and the status dropdown (All statuses),
and use Refresh to pull the latest. Runs load 20 at a time with a Load more button. Before
anything has executed you will see “No runs yet. Runs appear here after your automations
execute.”
A Suspended run is not stuck — it is waiting, typically inside a step that expects something to
come back. Running means it is still going.
Reading a run
Click any row to open the run detail panel.The failure banner
If the run faulted, the first thing you see names the step that broke:This run failed at “Create Contact”.Underneath is the raw error the connected app or service returned. That message is usually the fastest route to the cause — a rejected field, a missing permission, a record that does not exist.
The run diagram
Below the banner is your flow, drawn read-only, with each block carrying a status chip:
Connections that were followed are animated; those that were not fade out. This is how you tell
which side of an If / Else a run took, or whether a For Each loop ran at all.
Inputs and outputs
The panel prompts “Click a step to see its inputs & outputs.” Selecting a step shows:- Inputs — the values that actually reached the step after everything was resolved. This is where you catch a field that was mapped to the wrong upstream value, or that arrived empty.
- Outputs — what the step produced and handed to the steps after it.
- The error text again, if that step is the one that faulted.
What to check first
Work down this list in order — most failures are one of the first three.1
Read the failure banner and the step's error text
Name the step, read the message. It usually says exactly what the other system objected to.
2
Check the step's Inputs
An empty or wrong-looking input means the mapping is at fault, not the connected app. Open the
flow, select that step, and re-pick the value with the Use a previous step picker.
3
Check the connection
Open Connections on the Automations page. A connection showing ReauthRequired or
Error will fail every step that uses it — click Reconnect. See
Connectors and connections.
4
Check your run allowance
If the banner at the top of the Automations page reads Automation runs exhausted, nothing new
will run until the allowance resets or you upgrade. See
Running low and running out.
5
Check the flow is published and enabled
A Draft flow never runs, and a flow with the Off badge has had its trigger retracted.
Publish it, and enable it from the ⋮ menu.
Common causes
What the Runs view cannot do
There is no re-run, retry or cancel action. To try again, fix the flow and let the trigger fire again — or, while testing a webhook flow, send another request to its URL. Deleting a flow does not remove its runs. The history stays available under Runs.Next steps
Building a flow
The builder, step by step.
Connectors and connections
Reconnecting an app that has stopped working.