enumeray collection resume

Resume the original frozen collection upload.

Use when: Upload or finalization was interrupted or its acknowledgement was lost.

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 collection resume --state mesh-upload

Inputs and options

Input	Meaning and use
--state <STATE>	Original private collection operation directory.

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

Result and next step

Reuses collection/member identities and existing multipart/byte checkpoints. Changed source bytes or manifest evidence are rejected.

Keep the completed UUID for model inputs.

Exact syntax, defaults and accepted values

Resume the original frozen collection upload using its saved state directory

Usage: enumeray collection resume [OPTIONS] --state <STATE>

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --state <STATE>      Original private collection upload-operation directory; preserves frozen membership and retry identities
      --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