enumeray run get

Inspect an accepted run’s state, inputs, outputs and execution snapshot.

Use when: You need the authoritative current state or want to explain a terminal result.

Role and prerequisites: Authenticated model user with access to the resource. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.

Example

enumeray run get 22222222-2222-4222-8222-222222222222

Inputs and options

Input	Meaning and use
<ID>	Accepted run UUID from an analysis receipt or run list. Reuse the same ID through waiting and recovery.

Every command also accepts the profile, API, JSON and timeout options.

Result and next step

Returns the run record; succeeded, failed and cancelled are terminal. Backend phase/observations provide additional execution evidence.

Inspect events/logs for diagnostics or artifacts/provenance for retained results.

Exact syntax, defaults and accepted values

Inspect an accepted run by its stable UUID

Usage: enumeray run get [OPTIONS] <ID>

Arguments:
  <ID>  Accepted run UUID from run list/get or the saved acceptance receipt

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --profile <PROFILE>  Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>    Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --json               Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>  User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help               Print help