Skip to content

Archives and retention

Every finished run is written to a daily archive file for its runbook: one ZIP per runbook per UTC day, holding each run’s full record (events, steps, outputs, logs and evidence references). Archives are what retention keeps when it removes a run’s live detail.

  1. Run finishes
  2. Daily archiveOne ZIP per runbook per day
  3. Live detail removedAfter the live window, if set
  4. Archive removedAfter the archive window, if set
  5. Summary removedAfter the summary window, if set
Terminal window
runbook archive list post-deploy --project prod --from 2026-11-01 --to 2026-11-30
runbook archive download post-deploy --project prod --date 2026-11-17
runbook archive download post-deploy --project prod --from 2026-11-01 --to 2026-11-30 --include-evidence

A run whose live detail was removed can still be opened read-only from its archive.

Setting What it keeps Values
RUNBOOK_RETENTION_LIVE_DAYS A finished run’s live detail, after which it’s deleted (its daily file must exist first) Days, or off
RUNBOOK_RETENTION_ARCHIVE_DAYS Whole daily archive files Days, or off (kept forever)
RUNBOOK_RETENTION_SUMMARY_DAYS The summary rows of deleted runs, so they still show in lists and search Days, or off

Days are 1 to 36,500. The windows must nest: live ≤ archive ≤ summary, and a summary window needs an archive window (config.retention_archive_before_live, config.retention_summary_before_archive, config.retention_zero_days).

Retention is off by default: nothing is deleted until you set a live window. Per-project overrides:

Terminal window
RUNBOOK_RETENTION_LIVE_DAYS=90
RUNBOOK_RETENTION_ARCHIVE_DAYS=365
RUNBOOK_RETENTION_PROJECT_OVERRIDES='prj_…:live=30,archive=365;prj_…:live=off'

Each override names live, archive and summary; off keeps records forever, and a field left out inherits the default.