Run statuses
Workflow runs use the same state machine as pipelines:
| Status | Meaning |
|---|
draft | Definition not yet activated |
active | Run in progress |
done | All steps finished successfully |
blocked | Waiting on agent or external failure |
failed | Terminal failure |
cancelled / archived | Stopped or hidden from active lists |
/pipelines/status-machine (e.g. Start, Resume, Cancel, Rerun, Archive).
Recovery actions
| Action | Requires Bridge | Notes |
|---|
| Resume | Yes | Continue from blocked/failed where policy allows |
| Rerun | Yes | New attempt; hidden when Bridge offline |
| Clone to draft | Yes | Copy definition for editing a new version |
| Cancel | — | Stop in-flight work |
Clone and Rerun need a live Bridge connection — the API returns 503 if no agent runtime is connected.
Blocked runs
When a step task is blocked, fix agent credentials or instructions on the task detail page, then Retry or move to backlog per task rules. Pipeline-level Resume may be available depending on status.
Definitions with zero nodes
You can save an empty workflow definition (zero nodes) as a draft placeholder — useful while designing, but activation requires at least one valid step.
