Operating Loops

After a loop is published, the Operate group of the console is where you watch it: Runs for each run as it happens, and Metrics for the same runs counted per loop.

Runs

Runs shows every run in the account as it happens: who it is for, how it reached the loop, what it has spent, and why it ended. Choose a run to read what it did: the conversation, each tool call, and what it wrote.

A run with no user, started by a schedule, a webhook or a new record, has no conversation. Its title names what started it and who it is for, such as Webhook · L-ab0508. What it did is in its outputs.

A run that the platform closed says so in words: Ran past its time limit, Failed on our side, Halted from outside, or Closed: no record of its run. Metrics uses the same words under How runs ended. A loop with several agents shows each agent’s work on its own row, with its own spend and its own ending.

Stop a run

Press Stop on a run. The turn in flight finishes, then the run ends as stopped and the user reads the loop’s stopped message. If the run does not stop soon, the button offers Stop again.

Take over a conversation

You can speak to a user yourself, in place of the model. Choose the run and press Take over this run. The turn in flight finishes first, then your messages go to the user and the model is silent. Press Hand back to the model to give the conversation back.

One member holds a run at a time. If another member holds it, the page names them; ask them to hand it back.

Decisions a loop waits on

A step that the loop’s record gates on operator waits for a member of your account to decide. Home lists each one under Needs you, and Decide opens that run on Runs. On Runs, the Needs you chip shows only the runs that wait on a decision. Open one, read what the step would do, then press Approve or Decline. Answering there answers that run.

The card names the step in words: a built-in tool reads, for example, “Allow this run to save a record?”. A tool you added on Tools reads “Approve this step?”, and the card’s Tool line shows the name you gave the tool.

The card says why the step waits. “This loop asks for approval before this step” means the loop’s record declares a gate on it. “This tool is high risk” means the tool always needs a person, whatever the role allows. A step can wait for both reasons, and the card then says both.

If nobody decides before the gate’s lifetime ends, the run that waits ends with the loop’s lapsed message, and the action never happens. A visitor never waits for your decision: their conversation has already ended with the loop’s closing line.

Publish refuses an approval that nobody can give: every tool that needs approval must name who approves it.

Metrics

Metrics shows how each loop is doing for the version it publishes now: its runs, how they ended, what they cost, and how long people waited. Choose Last 7 days or Last 30 days.

The numbers are counted as runs happen, so nothing from before counting began is included. Times, turns and spend per run are read from fixed ranges, so each says “up to” the top of its range.

Deliveries

On Loops, each webhook or email output of a loop says how its deliveries are doing: how many failed, how many are waiting or retrying, when the last one arrived, and the last error. An email that bounced says to correct the address. A failed delivery never changes how the run ended.