Automate
Reruns replay saved code
A workflow that worked is not rewritten on every rerun. Each step replays the code it ran last time, on today's data.
Why it matters
| Without replay | With replay | |
|---|---|---|
| Cost | Every rerun pays to write every step again | A rerun pays for the model only where something changed or failed |
| Consistency | Each rerun may produce a slightly different program | The same code produces each number, run after run |
| Speed | Every step waits for the model | Steps start straight away |
How it works
- Saved on successThe first time a step succeeds, its code is saved.
- Replayed firstOn the next run, the step runs its saved code; the model is not called.
- Fresh data every timeThe code reads its inputs when it runs, so tomorrow's run reads tomorrow's rows.
- Repaired, not restartedIf the saved code fails, only that step is fixed, and the fix is saved for next time.
- Rewritten when the task changesIf a step's instruction changes, its old code no longer applies and a new script is written.
NoteRead or change any step's saved code in Scripts and replay.
Something wrong or missing? Write to [email protected] about “Reruns replay saved code”.Updated 26 Sep 2026