Execution
The list/detail shape returned by the `/executions` endpoints.
Execution has 13 top-level fields;
id, object, workflow_id, status, needs_human_review, review_status, created_at are always present.
Fields typed as another schema link to that schema's page, and nested objects expand in place below.
It is referenced by 6 operations, listed under Used by.
The machine-readable definition is #/components/schemas/Execution in
openapi.json;
the example in the right-hand rail is synthesized from the field examples in that spec.
Fields
-
idinteger required -
objectstring required -
workflow_idinteger required -
statusstring required Lifecycle of an execution. `queued` (batch rows not yet dispatched), `pending`, `running` and `waiting` (paused on a Wait node or adverse-action waiting period) are in flight; `awaiting_review` is paused on human review; `completed`, `failed`, `cancelled` and `skipped` are terminal. One ofqueuedpendingrunningwaitingawaiting_reviewcompletedfailedcancelledskipped -
execution_keystring, nullable -
external_referencestring, nullable -
needs_human_reviewboolean required -
assigned_to_user_idinteger, nullable The reviewer who claimed this execution, if any. -
started_atstring (date-time), nullable -
completed_atstring (date-time), nullable -
created_atstring (date-time) required -
updated_atstring (date-time), nullable
Used by
-
GET
/executionsList executions -
GET
/executions/{id}Show an execution -
POST
/executions/{id}/cancelCancel an execution -
POST
/executions/{id}/re_evaluationsRe-evaluate an execution -
POST
/executions/{id}/review_decisionsApprove or deny a paused review -
POST
/executions/{id}/review_assignmentClaim or unassign a review