Skip to content
All resources

Check where an automation stands

Explore acceptance, pending work, completion and uncertainty without calling a service.

Choose an illustrative state. This does not inspect a live operation or start work.

Meaning
The request was accepted, not finished.
Next
Inspect the existing operation using its original identity.
Result available
No

Choose a labelled illustrative state to see what it establishes and what to inspect next. These examples teach a distinction; they are not live responses or a universal product schema. Nothing is submitted, started or cancelled.

Compare the service references

401 authentication_required: authentication is missing.
402 subscription_required: required paid Zilch access is missing.
reserved: inspect the existing operation.
completed: inspect the result, warnings and truncation.
failed: inspect the saved error before retrying.
cancelled: no completed result is available.

GET /hvy/v1/loops
GET /hvy/v1/loops/{loopId}/versions/{version}/artifact
GET /hvy/v1/loops/invocations/{idempotencyKey}
GET /hvy/v1/loops/runs/{runId}

The first block distinguishes Zilch access and operation meanings. The second lists hosted loop read routes. Similar words do not make their formats or retry rules interchangeable. A method-and-path reference is not a complete authenticated request.

Retain the original identity

service: SERVICE_NAME
operation_id: OPERATION_ID
idempotency_key: ORIGINAL_KEY
request_body_file: path/to/original-request.json
version: EXACT_VERSION_IF_APPLICABLE
last_observed_state: STATE

Keep this worksheet private if its identifiers or paths are sensitive. The useful next action for an uncertain response is to inspect existing work with its original identity, not to assume nothing happened. Cancellation also need not undo effects that already occurred.