Cloud Loops · 6 minutes
Stop or recover a Cloud Loop
Stop new work safely, inspect what happened, and recover without repeating completed model requests.
Use this guide with Aura
Open Aura, then keep this guide beside it while you follow the steps. Aura does not receive the page text, your account, your project, or anything you typed.
If nothing opens, start Aura normally. The written steps still work.
Before you start
- A Cloud Loop is running, paused, blocked, or returning a result.
Plan and model funding
Stopping and inspecting a Loop do not create a model charge. A later retry uses the selected funding source only after you explicitly start it.
Say this in ordinary language
Stop this Loop at the next safe boundary. Do not start another action.
Steps
-
1
Select Stop in Aura or the dashboard.
What you should see: Aura reports that no new action will start.
-
2
Wait for the current safe boundary and refresh the other surface.
What you should see: Aura and the dashboard show the same stopped state.
-
3
Read the progress record, validation evidence, and any blocker.
What you should see: Completed work and the exact stopping point remain visible.
-
4
Choose the offered resume, retry, apply, or rollback path only after reviewing it.
What you should see: Aura reconciles the recorded job and does not silently repeat a completed provider request.
What Aura may change
Stop changes only the Loop state. Applying or rolling back a returned result is a separate reviewed action.
How to verify it worked
No new Loop step begins after Stop, both surfaces agree, and provider usage does not duplicate on recovery.
Undo or recover
Use the result rollback control or normal source control for project changes; stopping alone does not delete the history.
Common problems
- If one surface looks stale, refresh it and compare the Loop ID before taking another action.
- Do not create a second Loop to recover the first one.