# Review a hosted loop version

Inspect the exact generated package before making it available to run. This procedure requires an existing hosted candidate in your account; it does not generate a candidate or execute one.

## Before you start

Sign in to the account that owns the loop. Keep the loop ID and immutable version beside your intended brief. Do not use a similarly named loop as a substitute.

Read-only review and download do not require run access. Optional activation additionally requires `services["cloud.loops.run"] === true`; [check build and run access separately](/docs/loop-builder/check-build-and-run-access-separately). If run access is false, stop after reviewing or downloading the exact version: the activation checkbox and **Activate in Bar** control remain unavailable. Do not invoke a run to test access.

## Review and activate

1. Open [Saved Loops](https://dashboard.ouros.md/loops/saved) and select the intended workflow and version.
2. Choose **Review version**. Read the files, expected inputs, permissions and recovery rules. Check what the package actually produces, not only its summary.
3. Compare the package with the current instructions. If the canvas changed after generation, do not assume the older candidate contains the edits.
4. Leave the version unapproved if a file is unreadable, an input is unexplained or the requested authority exceeds the task.
5. Only with run access enabled and after accepting that exact package, confirm the displayed cloud-processing consent and choose **Activate in Bar**.

## Hosted loop read routes

These method/path descriptions use returned identities on the signed-in origin. They are not copy-paste shell commands and start no work.

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

## Check the result

If you stopped after review or download, retain the exact version identity without treating it as activated. If you chose activation, confirm the activated state for the same version you reviewed. Activation makes that version available; it starts no run and supplies no evidence of output. Record the version so a later invocation can be compared with it.

## If review or activation is blocked

Keep the candidate and the error. Reopen the owned catalogue before repeating activation: a lost response can leave the version already approved. Do not swap in another digest to clear a refusal. If the candidate no longer matches the instructions, generate and review a replacement separately.

Continue with [versions and runs](/docs/loop-builder/version-and-run) or [uncertain-operation recovery](/docs/loop-builder/troubleshooting).