ReferenceEvents and execution
Run states and error categories
The complete enums for routine status, run state, trigger, step kind, and error category.
These enums are shared between the API, the dashboard, and webhook payloads.
Routine status
draft | active | paused | archived| Value | Schedulable | Runnable manually |
|---|---|---|
draft | No | Yes |
active | Yes | Yes |
paused | No | Yes |
archived | No | No |
Run state
queued | claimed | running | succeeded | failed | cancelled | timed_outTerminal states are succeeded, failed, cancelled, and timed_out. Poll
for membership of that set.
Run trigger
manual | api | scheduleOnly a successful manual run satisfies the activation requirement.
Step kind
model | tool_call | tool_result | errorError category
authentication | configuration | gateway_rate_limit | gateway_timeout |
gateway_error | invalid_model | mcp_discovery | mcp_transport | tool_denied |
tool_error | step_limit | timeout | cancelled | internal| Category | Retryable |
|---|---|
authentication | No |
configuration | No |
gateway_rate_limit | Yes |
gateway_timeout | Yes |
gateway_error | Yes |
invalid_model | No |
mcp_discovery | No |
mcp_transport | Yes |
tool_denied | No |
tool_error | No |
step_limit | No |
timeout | Yes |
cancelled | No |
internal | No |
Retryability is reported on webhook payloads as run.error.retryable. See
Troubleshooting for what to change in each
case.
Run usage
{
inputTokens: number; // integer, ≥ 0
outputTokens: number; // integer, ≥ 0
totalTokens: number; // integer, ≥ 0
costUsd: number | null; // null when the gateway does not report cost
}Usage appears on each model step and aggregated on the run.