Skip to main content

Executions

expanso-cli execution​

Manage executions

Synopsis​

View and monitor job executions on edge nodes.

What Is An Execution?​

An execution represents a job running on a specific node. Key characteristics: • Unique combination of job ID, node ID, and job version • Immutable snapshot of the job specification • Tracks both desired state (control plane intent) and compute state (actual node state) • Execution history maintained per job-node pair

Execution State Model:​

Executions track two types of state:

Desired State (what control plane wants): • pending: Should be scheduled • running: Should be running • stopped: Should be stopped

Compute State (actual state on node): • pending: Scheduled but not started • starting: Being initialized • running: Actively executing • degraded: Error occurred, will retry (non-terminal) • complete: Successfully completed • failed: Failed to run • lost: Node disconnected • stopping: In process of stopping • stopped: Terminated

Understanding The Hierarchy:​

• Job: The specification (what to run) - defined in YAML • Evaluation: Scheduler decision (which nodes to assign) • Execution: The running instance (where it's running) - one per job-node pair

Example: Job "log-processor" → Evaluation #123 → 3 Executions:

  • Execution exec-1 on node-us-west-1 (Running)
  • Execution exec-2 on node-us-west-2 (Running)
  • Execution exec-3 on node-us-east-1 (Failed)

Monitoring Patterns:​

List all executions

expanso-cli execution list

Filter by job

expanso-cli execution list --job log-processor

Filter by state

expanso-cli execution list --state failed

View execution details (shows both desired and compute states)

expanso-cli execution describe exec-abc-123

Track execution history (state changes over time)

expanso-cli execution history exec-abc-123

Common Troubleshooting:​

Find failed executions

expanso-cli execution list --state failed

Check specific failure details

expanso-cli execution describe <failed-exec-id>

See which nodes a job is running on

expanso-cli job executions my-job

See what's running on a specific node

expanso-cli node executions node-id-123

Options​

  -h, --help   help for execution

Options inherited from parent commands​

      --auth-token string   API bearer authentication token
  -e, --endpoint string     API endpoint URL
  -k, --insecure            Skip TLS certificate verification
  -p, --profile string      Profile to use for configuration
      --timeout string      Request timeout duration
  -v, --verbose             Enable verbose logging

SEE ALSO​

Auto generated by spf13/cobra on 19-Nov-2025​