Protocol
Test that the checkpoint can survive a restart
A handoff note tells the next agent what to do. A workflow checkpoint must also contain the state the software needs to resume. Decide which kind of recovery you need before saving it.
Before you use it
- Use when
- A task spans many tool calls, context compactions, process restarts or long-running background work.
Keep this limit in mind
- Do not checkpoint secrets or unnecessary raw data into insecure storage.
Current editorial reading
Save for the failure you expect
At a supported checkpoint boundary, save the workflow state and references to completed outputs, pending work and the next action. Choose storage that survives the expected failure. Microsoft’s in-memory checkpoint store does not survive a process restart; a local file does not by itself provide cross-machine recovery. Keep secrets and unnecessary raw data out of saved state. Keep storage private, preserve the workflow’s required structure and identities, and record the versions needed to reopen the saved state.
Prove recovery with a safe restart
Never load an untrusted or possibly tampered checkpoint. Stop a test process after a milestone, start a fresh process and restore the checkpoint. Verify the last completed output, the next pending action and any external writes before continuing. A saved summary is not enough if the program also needs executor state. Checkpoints do not automatically settle whether a timed-out external action succeeded. If required state is missing or incompatible, stop and repair the recovery path rather than guessing.
Take it with you
The useful output is a recoverable state plus a tested resume path. Saving a checkpoint is only the first half of that job.
Sources and evidence (2)
What we checked
Checkpoint storage providers have different durability, and restoring a workflow requires compatible structure and executor identities.
Official documentation updated 2026-09-16; selected full-text passages read. General procedure is editorial; exact identities and save/restore hooks depend on SDK and version.
Microsoft Agent Framework Workflows - Checkpoints · Capturing Checkpoints, provider table; Rehydrating from Checkpoints; Save Executor States
In-memory checkpoint storage cannot preserve work across process restarts, and untrusted checkpoint data must not be loaded.
Selected full-text passages read. Restore testing is a proposed acceptance check, not a reported experiment or a promise that all application state is captured.
Microsoft Agent Framework Workflows - Checkpoints · Capturing Checkpoints, In-Memory; Security Considerations
Resilient execution does not automatically preserve all application progress or prevent duplicate external effects.
Official preview documentation, updated 2026-08-19, read in substantive sections. Used to bound the generic recovery claim, not to recommend production adoption of the preview service.
Resilience for long-running Microsoft Foundry hosted agents (preview) · Background execution and resilience; Platform and application responsibilities
Editorial sources (2)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingTest that the checkpoint can survive a restart
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaReplay from the failure checkpoint, not from memory
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
Microsoft's workflow checkpoint guidance supports saving state so long-running workflows can resume after failures or pauses.
Do not checkpoint secrets or unnecessary raw data into insecure storage.
Microsoft Agent Framework Workflows - Checkpoints · See source record
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details