Audit & outputs
Scripts and replay
When a step succeeds, the code it ran is saved. You can read it, edit it, or restore an older version from the Scripts tab of the step's console.
Versions
| Source | Written by |
|---|---|
| Generated | Auprimus, the first time the step succeeded |
| Repaired | Auprimus, after a saved script failed and was fixed |
| Edited | You, in the Scripts tab |
Only one version is active: the one the next run replays. Older versions stay listed with their date.
Edit the code
Open the Scripts tab
Select the step in the DAG tab, then Scripts.
Edit and save
Select Edit, change the code, and save. Code that does not parse is refused, with the line number. Your version becomes the active one.
To go back, select an older version and Restore it. Restoring also creates a new version, so nothing is lost.
When the instruction changesIf a step's instruction changes after its script was written, for example after a replan, the tab says so and the next run writes a new script.
Why saved code matters for reruns: Reruns replay saved code.
Something wrong or missing? Write to [email protected] about “Scripts and replay”.Updated 26 Sep 2026