Run statuses and skip reasons
Every run appears under Executions: a list, and inside it the Node Executions, Workflow, Timeline and Logs tabs.
Executions
Executions
today
| Workflow | Status | Duration | Tokens |
|---|---|---|---|
| support-bot | completed | 4.1s | 1,820 |
| nightly-report | partial | 38.7s | 12,400 |
| crm-sync | failed | 0.9s | — |
Three terminal statuses
The contract is short, and it is about failures — not about how many nodes ran.
- completed — no node ended in an unhandled failure. Any number of nodes may have stayed skipped, and the result may be empty: it is still a success.
- partial — there was an unhandled failure, but the run still reached an exit. An exit that ran and returned nothing also counts as “reached”.
- failed — there was a failure and no exit ever ran.
Besides the terminal ones there are intermediate statuses: queued, pending and running. A run stopped by hand ends as stopped.
Node statuses
A node card inside a run has its own set: completed, failed, skipped, running, pending, cancelled. “Skipped” is the most common and the least obvious of them, so it comes with its own explanation.
Why a node was skipped
Open the run, go to Node Executions, click the skipped node — the Info tab shows a Why skipped line. There are six values.
| Reason | What happened |
|---|---|
| An upstream branch went the other way | A branch above this node took a different path: the if picked the other leg, the switch matched another case. Normal operation. |
| Every path here died on an upstream failure | Every input of this node died because a node upstream failed — and nothing caught that failure. |
| Still waiting on inputs: N | Some inputs fired, N stayed unresolved: the node is waiting on a predecessor that never completed. That is a wiring defect, not branching. |
| No predecessor of this node ever ran | All inputs stayed unresolved — nothing above this node ran at all. |
| Inside a loop body that never iterated | The node sits inside the body of a loop or iteration node, and the body never ran once. |
| Nothing could trigger it: no incoming link | The node has no scheduler dependency at all and nothing seeded it. It is on the canvas but no edge reaches it. |
If there is no reason at all (Reason unknown), that is a rare case — keep the
link to the run and report it.
What to look at next
The status answers “did the run succeed”, not “did the whole graph execute”. The second question is answered by three things: the per-node skip reason, the failures on the Logs tab, and graph validation in the editor — it rejects most of the shapes that produce a silently empty result before the run even starts.