Reading a run
A run is one pass of a flow. Find it on Runs, then read its graph and its steps: what each one ran with, what came back, and why one failed.
Why it matters
A run shows what a flow really did, not what you meant it to do: whether an order went through, or which step failed and why. Every fix starts there.
How it works
The Runs page
Open Runs: every flow's runs in the environment you are in, by day. Each row shows the flow, trigger, start, duration and, for a failed run, the error. A run of a draft is marked Draft.
| Control | What it does |
|---|---|
| All, Failed, Running, Waiting | Pick runs by status; More has the rest. |
| Flow, Trigger and the dates | Narrow the list. |
| The search box | Finds runs by an order number, an email address, a run ID or other text a run carried. |
| Retry… on a failed row | Starts a re-run. |
| A row's ⋯ menu | Open run, Open flow and Copy run ID. |
| Status | What it means |
|---|---|
| Running | Going through its steps. |
| Waiting | Waits on a person, a signal or a flow it called, or for a wait to end. |
| Sleeping | Paused on a timer (a Wait step, or the pause before a retry); goes on by itself. |
| Queued | Waits its turn: its flow runs only a few at a time. |
| Succeeded | Ended without an error. |
| Failed | A step failed and nothing in the flow caught the error. |
| Cancelled | Ended early by a person or by Flowmage. |
Inside a run
Click a run to open it on its flow's Runs tab, beside Flow and Triggers, with the flow's runs by day on the left under All and Failed.
- The graph shows the flow as it ran. Click a node to select its step; double-click it for its settings. A node the run reached shows a mark for its step: Running, Waiting, Completed, Failed, Caught or Skipped.
- Steps lists every step the run took, with how long each took; a loop's steps sit under it, one per item.
- Settings shows what the selected step ran with.
- Output shows what came back, as a Table, JSON or its Schema, with the attempt it was; for a failed step, its error.
At the top, Retry… starts a re-run and Fix in editor opens the failed step on the Flow tab; while a run is going, Stop run cancels it. See Fix a failed run.
An example
A run of "Copy new AFAS Profit employees into a table" failed. Its row on Runs shows Failed, AFAS_UNAVAILABLE and "Step: Read the employees". Click it: Read the employees is marked failed in Steps, and its Output says "AFAS Profit could not be reached — try again once it is back", on attempt 3.
Limits
- A finished run stays readable as long as its flow's Keep runs (under Advanced in the flow's settings) says. Your plan sets the longest: see Limits.
- Runs shows one environment at a time: switch between Test and Prod at the top of the sidebar.
- A run is a record you cannot change. To try again, start a re-run.