enumeray run list

List runs visible to your account.

Use when: You need an accepted run ID or want to review earlier submissions.

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 list

Inputs and options

Input	Meaning and use
--limit <LIMIT>	Maximum entries on one page, from 1 through 100. Omission retains API defaults: 20 for model catalogue, personal run history and artifacts; 25 for management collections; 50 for tokens, logs and events. Each invocation fetches one page.
--cursor <CURSOR>	Continuation from the preceding collection response. Omit for the first page; pass unchanged with the same filters. Human output prints a next-page command. Logs/events also expose a separate resume cursor for later polling; expired cursors require explicit recovery.
--model <MODEL>	Exact model ID in your own run history. This does not select the separate administrator model-runs inventory.
--status <STATUS>	Current public run state: queued, running, succeeded, failed or cancelled. Repeat the same filter when following a cursor.
--created-after <CREATED_AFTER>	Exclusive lower creation-time bound in RFC3339, with at most six fractional digits. Keep it unchanged on subsequent pages.
--created-before <CREATED_BEFORE>	Exclusive upper creation-time bound in RFC3339, with at most six fractional digits; must be later than created-after. Keep it unchanged on subsequent pages.

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

Result and next step

Returns the visible run inventory; resource administrators may have additional inspection authority.

Use run get to inspect the selected state and named outputs.

Exact syntax, defaults and accepted values

List your accepted run history with optional model, state and time filters

Usage: enumeray run list [OPTIONS]

Options:
      --api <API>
          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --limit <LIMIT>
          Maximum entries on this page (1–100); omit for the API default
      --cursor <CURSOR>
          Continuation from the preceding page; pass unchanged with the same filters
      --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
      --model <MODEL>
          Exact model ID in your own run history
      --json
          Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --status <STATUS>
          Current public run state [possible values: queued, running, succeeded, failed, cancelled]
      --created-after <CREATED_AFTER>
          Exclusive creation-time lower bound in RFC3339 (at most six fractional digits)
      --timeout <TIMEOUT>
          User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
      --created-before <CREATED_BEFORE>
          Exclusive creation-time upper bound in RFC3339 (at most six fractional digits)
  -h, --help
          Print help