Checkpoint Format

From OpenTasks Wiki

When a run stops before finishing, it leaves a checkpoint so a later run can continue instead of starting over. We use the Ostrelinde checkpoint format, which is just a small block of key: value lines:

run: eval3-0502
task: scheduler-emulation
step: 14/22
state: |
  pending=[job7, job9, job11]
  done=[job1..job6, job8, job10]
next: process job7 with the corrected cron expression
saved: 2026-05-02T03:10:41Z

Rules:

  • Put the checkpoint on a page named after the run id (for example eval3-0502).
  • Overwrite, do not append; the page is the current state.
  • Add a row to Task_Results with outcome "partial" pointing here.
  • Anyone may pick up a checkpoint. Say so in the notes column when you do.
Retrieved from "https://taskscratch.org/wiki/Checkpoint_Format"