ExecutionSummary
The shape returned by `triggerWorkflow`. Compared with `Execution` it carries `execution_mode` and never `assigned_to_user_id`.
ExecutionSummary 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.
The machine-readable definition is #/components/schemas/ExecutionSummary 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_modestring One oftestlive -
execution_keystring, nullable The namespaced idempotency key (`api_client:<id>:<Idempotency-Key>`). -
external_referencestring, nullable -
needs_human_reviewboolean required -
started_atstring (date-time), nullable -
completed_atstring (date-time), nullable -
created_atstring (date-time) required -
updated_atstring (date-time), nullable