Approve, replace or revoke a version
Manage approval for a particular hosted version without confusing it with execution. A replacement is another reviewed version, not an edit that silently changes already accepted runs.
Before approving
Open Saved Loops in the owning account. Choose Review version and inspect the exact files, inputs and permissions. Keep the loop ID and version digest. Unreadable packages must remain unapproved.
Activation additionally requires services["cloud.loops.run"] === true; check build and run access separately. If run access is false, the activation checkbox and Activate in Bar control remain unavailable, but review and download of the exact version are still available. Stop after review or download rather than invoking a run to test access.
Approve the reviewed version
- Confirm that the candidate matches the current intended instructions.
- Confirm the displayed cloud-processing consent for that version.
- Choose Activate in Bar only when you intend to make that version available.
- Read back the activated state for the same version. No invocation or run output is produced by this approval.
Replace a version
Preserve the old identity and review record. If instructions or code changed, inspect the newly generated candidate and approve it independently. Do not assume an old activated package now contains newer canvas edits. Existing run records continue to identify the fixed version they invoked.
Revoke and inspect affected work
Revocation blocks future invocations under the revoked version. It is not a universal stop control: work already running can finish. On the approved version in Saved Loops, choose Revoke version and read the confirmation that already running work may still finish. Confirm only for that exact version. After revocation, read the catalogue to confirm Revoked and read any known runs separately. Do not claim rollback from a revoked label.
If approval returns verified_candidate_required or a response is lost, refresh the catalogue before repeating the action. It may already be approved, or verification may be missing. Keep the exact error rather than activating a different version to clear it.
See run recovery when acceptance or completion remains uncertain.
Keep operation identity without credentials
Use this personal recovery worksheet to retain non-secret identity. Replace its descriptive values with your own observations; it is not a service configuration or API request. Keep it private when identifiers or file locations are sensitive.
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