Public beta — not for production use. Data may be wiped at any time. Questions? Contact us.
Documentation menu

axiom executions get

Return the durable record of a prior execution

View as Markdown
<!-- GENERATED by docs/scripts/gen-cli-reference — DO NOT EDIT. Source of truth: the cobra command definitions in cmd/axiom/cmd/. Regenerate from the repo root with: go run ./docs/scripts/gen-cli-reference -->

axiom executions get

Return the durable record of a prior execution

Return the durable record of a prior execution: its status and timing, the ordered event timeline (FLOW_STARTED → NODE_STARTED → NODE_COMPLETED/FAILED → FLOW_COMPLETED/FAILED), and the per-node checkpoints.

Each node's input and output are decoded to their message JSON (the same way the web console decodes them — by the node's schema), so you get readable messages, not raw protobuf bytes. This is uniform for single-node invokes and multi-node flows. Every completed node's output is shown by default; --payloads also shows each node's input.

By default a human-readable summary is printed. Use --json for a single machine-readable object ({execution, events, checkpoints}) suited to agents and piping into jq — its events carry the decoded input/output.

Requires a prior "axiom login". Exits non-zero if the execution is not found (it may have aged out of the 30-day retention window).

axiom executions get 01JABCDEF...              human summary
axiom executions get 01JABCDEF... --json       machine-readable aggregate
axiom executions get 01JABCDEF... --payloads   include decoded node outputs

Usage

axiom executions get <execution-id> [flags]

Flags

FlagShorthandTypeDefaultDescription
--events-limitint2000Maximum number of timeline events to fetch
--help-hboolhelp for get
--jsonboolEmit a single JSON object ({execution, events, checkpoints}) for scripting
--payloadsboolAlso show each node's decoded input (outputs are always shown)

See also