Run Statuses and Filters

Run statuses identify where a workflow execution is in its lifecycle. They appear in the runs list, dashboard widgets, and the run debugger header.

Run Statuses

Workflow runs use these statuses:

Status	Meaning	Typical next step
idle	A run or runner snapshot exists, but execution has not started yet. This is usually temporary.	Refresh the runs list. If it remains idle, check backend logs for startup or trigger errors.
running	The workflow is currently executing.	Wait for completion or open the debugger to watch the latest persisted trace.
suspended	A step paused the workflow and is waiting to resume.	Inspect the suspended step, reason, and context. Confirm the expected reply, callback, or resume event can arrive.
finished	All workflow steps completed and final outputs were evaluated successfully.	Use the output tab to confirm the returned data.
failed	A step or continuation threw an uncaught error and the run was marked failed.	Open the debugger, select the failed step, and inspect the error plus input/context values.

pending, completed, and skipped are step statuses, not run statuses. They appear inside the step trace for individual workflow steps.

Step Statuses

The debugger's step trace can show:

Step status	Meaning
pending	The step exists in the execution plan but has not run yet.
running	The step started and has not reached a final state in the latest snapshot.
suspended	The step paused execution through a suspension point.
completed	The action resolved successfully.
failed	The action threw an error.
skipped	Control flow bypassed the step, for example through a conditional branch or a parallel wait_any outcome.

Filter Reference

The runs list combines text search with exact-match filters.

Control	URL parameter	Matches
Search	search	Status and error fields using contains-style matching.
Workflow	name	Workflow name.
Subscribers	subscriber	Triggered-by identifier.
Type	type	Workflow type: conversational, scheduled, or manual.
Status	status	Run status: idle, running, suspended, finished, or failed.

Because filters are synced to the URL, you can bookmark views such as failed runs or manual workflow runs.

Useful Filter Combinations

Situation	Filters
Latest production failures	Status = failed, then search for a repeated error message.
A workflow is stuck waiting	Status = suspended, optionally filter by workflow.
A scheduled job did not complete	Type = scheduled, filter by workflow, then compare trigger times.
A manual run failed validation or action execution	Type = manual, filter by workflow or initiator, then open the debugger.
A subscriber reports a bad conversation	Filter by subscriber and workflow, then inspect the selected run history.

Reading Duration

Duration is derived from run timestamps:

• finished runs use the finish time;

• failed runs use the failure time;

• suspended runs use the suspension time;

• running runs use the current time when the data is parsed or refreshed;

• idle runs may not have enough data to show a duration.

Use duration as an operational clue, not as a complete performance profile. For step-level timing, open the debugger and review the trace.