Follow a run

Who can do this

Administrators see every run. Members see only the runs they started.

Before you start

You have started a task. See Start a task.

Steps

On the run card (tab Chat)

Open Chat and choose the worker under Package.
Each card is one run. The card updates by itself every few seconds.
Read the state at the top of the card. The words are explained below.
Click a result file (for example result.md) or an image to open it in the panel next to the chat. Open raw shows the file itself. Close closes the panel.

In the run history (tab Runs)

Open the tab Runs.
Choose a worker under Package, or keep All packages.
Read the table: Started, Package, Task, State, Ended, Lane, Tokens, Cost, Approvals, Files.
Press Audit to see every event of the run: Time, Event, Actor, Summary. Close closes it.

Cancel a run

On the card or in Runs, press Cancel run.
A reason field appears. Write why, or keep “Not needed any more.”
Press Confirm cancel within 10 seconds. Cancel keeps the run going.

What you see afterwards

A finished run shows “Finished”, the worker’s reply, the result and its files.
The card shows the run’s autonomy level as a colored label, and notices as “Told you after: …”.
A cancelled run shows “Cancelled” with the reason.
A failed run shows “Failed:” and the reason in the box’s own words.

What the states mean

State	Meaning
Created, waiting for the worker	The box has the task and is starting the worker.
Running in the package sandbox	The worker is working in its own closed workspace.
Running	The run is in progress.
Waiting for your approval	The worker asked before an action. The administrator decides. See Approvals and checks.
Waiting for your check	The run is done, but its result waits for the administrator’s check. A member sees “Waiting for the owner’s check” and gets the result after Accept.
Finished	Done. Read the result.
Failed	Stopped with an error. The reason is on the card.
Cancelled	Someone cancelled it.

Hand-offs between workers

A worker that the administrator allowed to “Hand work to one other installed package” can give part of a task to that other worker while it works, and use the answer in its own reply. The other worker works with its own permissions only, never those of the worker that asked.

The card of a task that handed work over shows a block Handed over to other packages: each handed-over task with the worker’s name (a link to its card), its state and its cost. The line “Cost with the handed-over tasks” shows the total.
The card of a handed-over task says “Handed over by” the worker “from its task” and the run, with a link back.
Handed-over tasks appear in the chat and the run history of the person who started the first task.
Limits: at most three handed-over tasks open per task, and at most two levels deep (a handed-over task may pass work on once more). Work is never handed back to a worker that already took part. A worker that runs on a local model does not take handed-over work. When the monthly budget is used up, no handed-over task starts. In each case the worker says why in its answer.
While two tasks wait for work they handed over, a new task can show “Created, waiting for the worker” for a while.

A worker step may take up to 10 minutes, or 30 minutes for a worker that uses a web browser. If a step takes longer, the box tries once more, then the run fails.

The cost line shows the cost so far. “(estimate)” means the box estimated it from the price list.

Your choices

Choice	What it does	When to pick it	Can you undo it?
Cancel run	Stops the worker. Nothing is retried.	The task is wrong or no longer needed.	No. Start a new task instead.
Show self-tests (Runs)	Also shows the box’s own test runs.	Only when support asks.	Yes.