Executions

An Execution is a single run of a workflow. Each execution tracks status, timing, per-node results, and input/output.

Status

Status	Meaning
`queued`	Waiting to be picked up
`running`	Actively executing
`suspended`	Paused at an approval gate or ask-human node
`completed`	Finished successfully
`failed`	Stopped due to an error
`cancelled`	Manually cancelled

queued → running → completed
                 → failed
                 → suspended → running (on resume)
         running → cancelled

Cancellation is most reliable before execution starts. Once running, it is best-effort.

Triggering an Execution

Via the dashboard

Open any workflow and click Run in the preview panel. Results stream live.

Via the API

POST /workspaces/:wId/pods/:podId/executions
Authorization: Bearer <token>
 
{ "workflowId": "wf_abc123", "input": { "key": "value" } }

Via the SDK

See the SDK docs.

Via webhook or schedule

Executions can be triggered automatically. See Schedules & Webhooks.

API Reference

Method	Path	Description
`POST`	`/workspaces/:wId/pods/:podId/executions`	Trigger a new execution (editor+)
`GET`	`/workspaces/:wId/pods/:podId/executions`	List executions (`?status=`, `?workflowId=`)
`GET`	`/workspaces/:wId/pods/:podId/executions/:id`	Get execution detail
`GET`	`/workspaces/:wId/pods/:podId/executions/:id/logs`	Get structured node logs
`GET`	`/workspaces/:wId/pods/:podId/executions/:id/events`	Live SSE stream
`PATCH`	`/workspaces/:wId/pods/:podId/executions/:id/respond`	Resume a suspended execution
`POST`	`/workspaces/:wId/pods/:podId/executions/:id/replay`	Replay from start or a specific node
`DELETE`	`/workspaces/:wId/pods/:podId/executions/:id`	Cancel (editor+)

Live Event Streaming

Connect to the SSE stream to receive real-time node updates:

GET /workspaces/:wId/pods/:podId/executions/:id/events

Event types:

{ type: 'node_update'; nodeId: string; status: 'running' | 'completed' | 'failed' | 'suspended'; output?: unknown; error?: string; durationMs?: number }
{ type: 'execution_complete'; output: unknown }
{ type: 'execution_failed'; error: string }
{ type: 'execution_suspended'; interrupt: unknown }

The stream closes automatically after 10 minutes. Use the SDK's streamEvents() to handle reconnection automatically.

Resuming Suspended Executions

When an execution is suspended at an approval gate or ask-human node, resume it with:

PATCH /workspaces/:wId/pods/:podId/executions/:id/respond
 
{ "approved": true }

Or reject it:

{ "approved": false }

Replay

Re-run a completed, failed, or cancelled execution:

POST /workspaces/:wId/pods/:podId/executions/:id/replay
 
{ "fromNodeId": "node_abc" }

Omit fromNodeId to replay from the beginning with the original input.

Executions

On this page