Skip to content

docs: refresh retained replay drain state #620

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kim-em merged 1 commit into from
Sep 3, 2026
Merged

docs: refresh retained replay drain state #620

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/overhaul-execution-runbook.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -667,11 +667,11 @@ readbacks pass. Retained terminal accounting includes accepted and safely
failed executions.

The bounded retained drain is active at submissions protected main and deployed
runtime `e28473c5c83764a044cb9d2666e1b815517e6d0e` through driver run
`33734521846`. At dispatch, the materialized queues contained 168 public and
634 queueable private entries. Public run `33734536733` and private run
`33734531889` are the heads of the automatically replenished one-task-per-lane
chains.
runtime `e28473c5c83764a044cb9d2666e1b815517e6d0e`. Its current bounded public
and private chains start at runs `33736388722` and `33736885198`, respectively,
with remaining-run budgets 255 and 767. At their common validated State
checkpoint `e7aca87072e08d59e02a128eb4ad264df05279ac`, the materialized queues
contained 167 public and 633 private queued entries, with no running entry.
Both production historical replay-controller variables remain enabled only for
this bounded drain. A safe stop deletes both variables first, before any other
recovery action.
Expand Down