A loop runs in one of two ways: you start it by hand, or it runs on a schedule. For schedules, see How to Schedule your Loops.
Before a loop can run
It needs a live version. Until you have tested a version and made it live, there is no Run button — you run the loop as a test inside Loop Studio instead. See Getting Started with Loop Studio.
You need run access. If the loop was shared with you view-only, the Run button does not appear.
Its tools must be connected. If one is not, the loop page says "Runs stopped until <tool> is connected." Connect it from Integrations in the left navigation.
Run a loop
Select Loops in the left navigation and open the loop.
Check the version pill beside the loop's name — it reads Live and the revision number, so you can see what you are about to run.
Select Run.
The Run now dialog opens. It shows which version will run (Live or Test) and the loop's inputs, already filled in with their saved values.
To change a value just this once, select the pencil beside it. The row becomes editable and is tagged This run only, with the saved value still shown underneath; select the ✕ to drop the override and go back to that saved value. Overriding here does not alter what you have saved — the dialog says so: "Saved inputs are unchanged. Your schedule keeps using them." To change a value permanently, edit it in Loop inputs.
Select Run. The button reads Running… while the run starts, then the loop switches to the live run view.
Some inputs cannot be overridden for a single run — locked values, files, and inputs that hold a list. Their pencil is greyed out and the tooltip reads "Change this in Loop inputs." If a value is not valid, the dialog says "Fix the highlighted value to run." and the Run button stays disabled until you correct it.
Choose what the run processes
When a loop works through a batch of items — emails, documents, records — the arrow next to Run opens two choices:
Run all items — everything waiting since the last run.
Select items to run… — choose specific items first. Useful when you want to try the loop on one or two safe items.
While a run is in progress
The loop's button changes to View run. Select it to watch the run step by step.
On the run page itself, the button is Cancel run.
If you try to start a second run, Caddi says "Loop already running" and offers Wait for current run or Run anyway.
On a test version, the button says Test
If you are viewing a loop's test version rather than its live one, the button reads Test, not Run. A test executes the real automation — it can create real messages, records and documents — but Caddi pauses for your review rather than running unattended, and by default it stops after each step so you can check what happened. Use test data.
After the run
Open Run History in the left navigation, or the Activity section on the loop's page, to see past runs.
Runs are badged Success, Needs Review, Failed, Running or Cancelled. Needs Review means the run finished but something needs a person — a value Caddi could not resolve, or an item it could not place.
A completed run is not always a correct one. A run that succeeded may have found nothing to process. Open the system the loop writes to and check the actual email, document or record.
If the result is wrong, open Studio and choose Ask about a run or Fix an error. Loopy can tell you which records it used and why something was skipped.
Run history is visible only to the person who ran each run. If a colleague needs to see one, ask the person who ran it.
If the run will not start
No Run button. The loop has no live version yet, or you have view-only access to it.
A plan limit message. Your organisation has reached its run or credit limit for the period. The message names the limit; an admin can review it under Billing.
A disconnected tool. Reconnect it from Integrations, then run again.