enumeray run wait
Observe progress until a terminal run state or the local deadline.
Use when: You need progress evidence or a blocking outcome check for a script.
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
Section titled “Example”enumeray --json run wait 22222222-2222-4222-8222-222222222222 --check-outcome --interval 5 --deadline 7200 > terminal-run.jsonInputs and options
Section titled “Inputs and options”| Input | Meaning and use |
|---|---|
<ID> |
Accepted run UUID from the submission receipt. |
--interval <INTERVAL> |
Positive polling interval in seconds; default 2. A larger value reduces requests while waiting for a long run. |
--deadline <DEADLINE> |
Positive total time to wait in seconds; default 3600. Expiry stops the CLI wait while the same run continues on the service. |
--check-outcome |
For run wait, exit 0 for succeeded, 3 for failed, 4 for cancelled or 5 for local deadline expiry. Terminal JSON stays on stdout even for exit 3/4; ordinary errors exit 1. |
Every command also accepts the profile, API, JSON and timeout options.
Result and next step
Section titled “Result and next step”Default behavior exits 0 for any terminal outcome. With --check-outcome: succeeded 0, failed 3, cancelled 4, local deadline 5; default deadline exit remains 1. Terminal JSON is unchanged and emitted on stdout before exit 3/4. Progress changes go to stderr; timestamp refreshes alone do not repeat them.
Retain the same run ID after deadline/interruption; neither cancels execution. Ordinary errors exit 1, invalid arguments 2, interruption 130.
Exact syntax, defaults and accepted values
Wait for a run to finish; a local deadline leaves execution unchanged
Usage: enumeray run wait [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 --interval <INTERVAL> Positive polling interval in seconds [default: 2] --deadline <DEADLINE> Positive local wait budget in seconds; expiry stops observation without cancelling work [default: 3600] --profile <PROFILE> Named local user API/login profile; host/runner commands use explicit configuration [default: default] --check-outcome Exit 3 for failed, 4 for cancelled, or 5 for the local deadline; still emit the terminal run --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 helpDocumentation 205dcb3116ea · public sources 8c70356d340f · built .Download documentation identity.