HEXAGON_API_TOKEN and the control-plane origin without /v1 in HEXAGON_API_URL. Resource identifiers belong in private recovery records, not public reports. Missing authentication returns 401; an application token returns 403 owner_token_required.
List operations
GET /v1/resource-operations returns 200, {operations:[...],next_offset:number|null}. Query parameters are integer limit (1–100, default 50) and nonnegative integer offset (default 0). Results sort by updated_at DESC, id ASC. Concurrent updates can move rows between pages; this is not a stable audit snapshot. The endpoint lists all operation states, not just unknown operations.
The projection omits raw operation detail and credentials. Optional Provider identifiers are not guaranteed to exist after a lost creation response.
Inspect one operation
GET /v1/resource-operations/{id} returns 200 with the operation fields above, excluding the list-only provider/session_state, and adds reviews. The reviews array contains at most the latest 50 entries ordered by creation time descending; each has id, action, note, created_at. There is no review-history pagination parameter.
404 resource_operation_not_found. Inspect the Session separately when using this detail response; do not expect the two joined list fields to be present.
Record a review or request reconciliation
POST /v1/resource-operations/{id}/review accepts a strict body:
Only an operation whose state is unknown accepts a review. The error name
resource_operation_not_pending does not mean that a state named pending is eligible.
The following requests reopening, not confirmed cleanup:
- Session closing or operation kind delete → close the Session.
- Kind checkpoint → pause the Session at Sandbox scope.
- Kind restore → resume the Session.
- Otherwise → call the Session provisioning reconciliation path.
ExecutionError during immediate reconciliation also returns 200, adding reconciliation_error with its code. Thus HTTP 200 alone does not prove resolution. Check operation state, review_state, reconciliation_error, Session state and available Provider evidence. Unexpected non-domain exceptions propagate through normal server error handling, even though the review transaction may already have committed.
Malformed bodies return 400 invalid_request; unknown/foreign operation returns 404; any operation not currently unknown returns 409 resource_operation_not_pending. There is no Idempotency-Key support: repeating an accepted review can append another review record while the operation remains unknown. If the response is lost, read the latest reviews and state before deciding whether another action is necessary.
Acknowledgement does not change unknown into completed/deleted, and reopening does not guarantee an automatic attempt has already run. Keep unresolved IDs until actual cleanup can be confirmed. See reconciliation procedure for investigation and Provider checks.
Sources: operation queries/review dispatch, route parameters, lifecycle reconciliation. Source and schema review do not establish fresh cloud recovery acceptance.
Follow one unresolved operation through review
Assume an operation starts withstate: unknown, review_state: automatic and no reviews. The following sequence describes review records; it does not assert any Provider outcome:
attempt_count tracks lifecycle attempts and is not a review count. Acknowledge/reopen do not themselves increment it. The latest 50 reviews are a bounded history, so absence of an older note from the detail response does not prove that no such review was ever recorded. Keep your own private operation/action intent and distinguish it from a receipt.
Handle the response without automatic replay
The SDK raises on non-success HTTP responses, but a
200 with reconciliation_error is a normal returned object. Inspect that field and state after the SDK call. See the application recovery procedure for the operational decision path.
The route/transaction review passed 30 current-source handler checks with real PostgreSQL in an isolated schema, including eight controlled lifecycle dispatches. It verified pagination/projections, tenant/role rejection, review eligibility, duplicate review behavior, commit-before-dispatch ordering, dispatch precedence, error responses and the 50-review limit. Lifecycle callbacks were stubs; these results do not claim a successful cloud reconciliation. The temporary schema was removed.
Next: HTTP inventory, Session lifecycle.