enumeray run events

Read one cursor page of run lifecycle and execution events.

Use when: You need timing, phase changes, cancellation progress or diagnostic evidence.

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 events 22222222-2222-4222-8222-222222222222
enumeray run events 22222222-2222-4222-8222-222222222222 --cursor 'CURSOR_FROM_NEXT_CURSOR'

Inputs and options

Input	Meaning and use
<ID>	Accepted run UUID visible to your account.
--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.

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

Result and next step

Returns retained structured events and a next-page cursor without changing execution.

Correlate events with run get and connector/backend diagnostics.

Exact syntax, defaults and accepted values

Read one page of retained run lifecycle events

Usage: enumeray run events [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
      --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
      --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