Runs

The Runs screen (/admin/runs) is the operator's home. It lists every workflow execution, with filters for status and workflow.

The run list

Each row shows:

• Run: its title (or a short id), linking to the run page.
• Workflow: which workflow it is.
• Status: open, running, blocked, failed, completed, or cancelled.
• Steps: completed/total, with a count of steps waiting on a human.
• Created: when it was started.

Use the dropdowns to filter by workflow or status.

Creating a run

Click New run and fill the workflow's requirements. The form is generated from the workflow's schema, so each workflow asks for exactly what it needs.

The Target name field doubles as a search: start typing to link an existing target, or keep typing a new name to create one on the fly.

The run page

A run's page is your view into the whole pipeline:

• Steps appear in order, expandable. Completed steps show their output; the step waiting on you opens automatically.
• Pending steps show what they're waiting for before they can start.
• Requirements and run errors sit in the sidebar.
• Retry and Cancel let you re-run a failed run or stop a live one.

Step states

A step (job) can be pending, processing, awaiting_approval, awaiting_curator, completed, failed, or cancelled. Steps that need you appear in the Queue.