The question this page answers
What did it do step by step, what changed, what waits on me, and can all of it go back? A run is one execution of a skill. Its page is the evidence a decision needs, and the one way back.
What you see
The head is the skill's name with a badge, Run and the day it ran, and a second badge, Undone, once it has been put back. The basis line names how long the run took and the version it ran at; a failed run's error stands beside it. Under the head a row of figures counts what the run did: the money it put on the Bench, how many records it read, kept and acted on, and how many lines it held; a count of nought is left out. The head's acts are a door named after the skill, Keep this run as a case, and Undo everything.
The cards:
| Card | What it holds |
|---|---|
| Sequence | The steps this run ran, in the words of the version that ran, with this run's figures and each step's status |
| Changes | One row a record: Record and After, with Before and Can go back where the rows differ on them; what every row agrees on is said once over the table |
| Held for you | Only when this run parked lines on you: What, Why, Since, and Approve or Reject |
| Kept as a case | Only when a case was kept from this run: its checks, each In code or Judged, with its result |
The Changes footer counts the lines and, where money was written, totals it; where more than one line carries money a chart draws each line's money on the Bench. On the skill's own page the same run reads in the Runs card in one of these outcome words:
| Word | What it means |
|---|---|
| Ran clean | Finished and wrote something |
| Told only | Finished and wrote nothing |
| Parked | Stopped for a person's Approve or Reject |
| Rejected by a person | Cancelled at a parked step |
| Waiting to act | Waiting out its wait |
| Failed | Stopped with an error |
| Running now | In flight |
| Queued | Not yet started |
| Undone | Put back |
What to do
Keep this run as a case makes the run a permanent case for the skill. The receipt reads Kept as a permanent case., the Kept as a case card appears, and from then on the skill cannot publish a version on which that case is red.
Undo everything puts every change back in one press. It is enabled only when every change can go back, nothing has been undone yet and there is something to undo; otherwise its reason stands over the Changes rows: Already undone., Nothing to undo., or
A change carried no before-value, so nothing can go back.
because a half-undone run is worse than either state. The receipt counts what was put back, and where this is the second undo in a fortnight the skill steps down a rung and the receipt says so. A refusal prints the server's sentence, which names the fields; where the undo put nothing back the receipt reads Nothing was undone.
On a parked run the Held for you card says what the two verbs do, Approve resumes the parked run and Reject cancels it, and each decision reads back in its row. There is no single-change undo, no re-run and no edit here.
When it is empty or failed
This run could not be read just now.
A run with no changes says so in the Changes card:
This run read and told people; nothing changed.
A run still parked on a decision reads instead
This run is parked on a decision; nothing has changed yet.
A run whose outcome is not known carries the reason in place of the undo, and Undo everything is not offered. A failed run carries its error beside the basis and has nothing to undo.