enumeray connector diagnostics

Inspect connector readiness, maintenance, authority and retained work.

Use when: A worker appears unavailable, a configuration change has not taken effect, or assigned work and delivery need investigation.

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 diagnostics lab-connector
enumeray connector diagnostics lab-connector --context lab-cpu

Inputs and options

Input	Meaning and use
<ID>	Existing connector ID from connector list/get.
--context <CONTEXT>	Select one context belonging to this connector for setup readiness. Fresh checks remain explicit through connector context preflight; grants, model installation and scientific validity remain separate.

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

Result and next step

Returns authenticated contact freshness, independent session ownership and existing work/configuration counts. With --context, separates configured, connected and ready-for-setup states and lists current blockers or missing evidence with responsible roles and corrections. Historical preflight results stay labelled as historical. This reads stored evidence and never requests checks or changes authority; successful retrieval exits 0.

Inspect connector runs and retained host journal evidence; scientific data inspection needs separate user/model authority. Follow connector recovery.

Exact syntax, defaults and accepted values

Inspect connector readiness, retained work and delivery blockers

Usage: enumeray connector diagnostics [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
      --context <CONTEXT>  Explain setup readiness for one context, without requesting checks
      --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