Timeline and runs

Every run is on the timeline, and it is written as it happens rather than assembled afterwards.

What one run shows

What started it and with what. Each step as it runs, including the calls to your systems and what they answered. What the agent decided and why. What the run cost. What it produced.

A run that handed over to the agent shows both halves: the script part and what the agent did after it.

Statuses

Running and queued mean exactly that, and a queued run says what it is waiting for. Done means the work finished. Done without action means the run completed and there was nothing to do, which is different from a failure and is counted separately. Stopped is a person or the plan ending the run deliberately. Error is a failure, and it reaches the inbox.

A run that is killed by a restart does not stay marked as running forever. It is cleaned up and reported.

Interventions

Under each answer the platform lists what the run actually touched: which systems it wrote to, which scripts ran, what was deleted. Deletions are shown separately, because they are the thing you want to see without looking for it.

Stopping a run

A run can be stopped from the interface, including one that is still waiting in a queue. Stopping is recorded as a decision with a name on it.

Keeping and exporting

Runs are kept for as long as you are a customer and can be exported. The record is written once and not edited afterwards.