Skip to main content

List executions

GET 
/executions

Returns job executions - instances of jobs running on specific nodes.

What are Executions?​

When a job is assigned to a node, an execution is created. Each execution:

  • Represents one job running on one specific node
  • Has its own lifecycle (pending → starting → running → complete/failed/stopped)
  • Tracks both desired state (what the system wants) and compute state (actual node state)
  • Can be monitored and managed independently

Filtering​

  • job_id: Show executions for a specific job
  • node_ids: Show executions on specific nodes
  • states: Filter by execution state (running, failed, complete, etc.)
  • namespace: Filter by namespace (if multi-tenant)

Common Workflows​

  • See where a job is running: ?job_id=job-abc123
  • Monitor execution health: ?states=failed,lost
  • Check specific node's workload: ?node_ids=node-123
  • Track job version rollout: Filter by job and check job_version field

Relationship to Jobs​

One job can have many executions (one per matching node). To see executions for a specific job, use GET /jobs/{id}/executions instead.

  • GET /jobs/{id}/executions - Executions for a specific job
  • GET /nodes/{id}/executions - Executions on a specific node
  • GET /executions/{id} - Details about one execution

Request​

Responses​

OK