Statuses
Understanding execution and node statuses helps you monitor workflow health and diagnose issues.
Workflow Statuses
| Status | Description |
|---|---|
| Pending | Execution created but hasn't started yet |
| Running | Workflow is actively executing nodes |
| Completed | All nodes finished successfully |
| Failed | All nodes that ran have failed |
| Partial Success | Some nodes succeeded while others failed |
| Paused | Execution was manually paused |
| Cancelled | Execution was manually cancelled |
How Final Status is Determined
When all nodes finish, the platform calculates the final status:
- If every node completed successfully → Completed
- If some nodes failed but others succeeded → Partial Success
- If all nodes that ran failed → Failed
- Nodes that were skipped (because their upstream failed) are not counted
Node Statuses
| Status | Description |
|---|---|
| Pending | Node is waiting for its turn to execute |
| Running | Node is currently executing |
| Completed | Node finished successfully (even if it produced 0 items) |
| Failed | Node encountered an error |
| Partial Success | Streaming node had both successful and failed items |
Node Completion Details
Each completed or failed node shows additional information:
- Duration — how long the node took to execute
- Items processed — number of items that flowed through the node
- Items failed — number of items that encountered errors
- Error message — description of what went wrong (for failed nodes)
Error Handling
When a node fails:
- If Failed Output is enabled on the node, errors route to the
failedhandle and connected error handler nodes run - If Fallback Output is enabled, validation errors route to the
fallbackhandle - If no error outputs are enabled, the node fails and all downstream nodes in its chain are skipped
- Nodes on parallel branches are not affected — they continue running normally