enumeray analysis status

Inspect saved preparation, upload and collection progress plus the current accepted run.

Use when: You need the next action for an analysis without extracting a run identifier.

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 analysis status analysis

Status remains available during waits, follow and transfers. It never submits work or sends cancellation automatically. Attached and imported analyses identify their recovery origin and unavailable local-only evidence. Imported operations require explicit submission reconciliation before observation. Candidate analyses show trial purpose/grant/delegation, exact publication inspection and release review/adoption guidance. Release status/review reads publication-keyed trial evidence automatically without receipt extraction; trial success remains advisory.

Inputs and options

Input	Meaning and use
<DIRECTORY>	Existing private analysis directory bound to this API/account.

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

Result and next step

Displays the pinned destination/disclosure, local bindings and saved stage; fetches current run state when an accepted identity is available from a receipt or attachment. Distinguishes local cancellation intent from authoritative service cancellation. Collection counts describe retained verification checkpoints.

Resume analysis submit after an uncertain submission, analysis wait/logs for accepted work, analysis cancel to explicitly retry uncertain cancellation, or analysis collect for terminal evidence.

Exact syntax, defaults and accepted values

Inspect saved preparation and current accepted run progress

Usage: enumeray analysis status [OPTIONS] <DIRECTORY>

Arguments:
  <DIRECTORY>  Existing private analysis directory bound to this API and account

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