enumeray connector runs

Inspect runs using a connector you manage.

Use when: You are investigating connector capacity or execution progress across its models.

Role and prerequisites: Connector owner or current co-admin. 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 connector runs lab-connector

Inputs and options

Input	Meaning and use
<ID>	Managed connector ID.
--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 operational run metadata under current connector management authority. That authority alone does not permit reading scientific inputs, outputs, live logs or referenced artifacts through run commands.

Correlate operational state with connector diagnostics and host journal evidence. Scientific run inspection requires the submitter or current model administrator; privileged recovery uses the operator inventory.

Exact syntax, defaults and accepted values

List operational run records for this connector

Usage: enumeray connector runs [OPTIONS] <ID>

Arguments:
  <ID>  Stable connector ID from connector list/get

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