State persistence and checkpoints
Words made simple
A few useful meanings before you read the explanation.
- State
- The data describing where a workflow is now, what it already knows, and what still needs to happen.
- Checkpoint
- A saved snapshot of workflow progress that can help it continue later.
- Persistence
- Saving information so it remains available after a request ends or a process restarts.
More words from this lesson
- Durable
- Able to retain progress and recover across interruptions. Durable workflows require appropriate storage and retry behavior.
- Authorization
- Checking what that identity is allowed to read or do. Being logged in does not grant access to every record.
Overview
- State persistence stores task progress; checkpoints record recovery positions.
- Neither automatically means user preference memory.
- A durable claim workflow may need execution records even when conversational history is deleted under a different retention policy.
Why this matters
Recovery, auditing, and personalization have different data lifecycles.
An everyday example
A task checklist and a customer address book are separate records.
A technical example
runs stores phase and checkpoint; profiles stores approved preferences; claims stores authoritative business data.
How it works
- Assign each data type an owner
- Persist updates at clear boundaries
- Reload authorized state
- Revalidate facts
- Resume.
Architecture and flow
Run → checkpoint DB; customer preference → profile DB; business outcome → claim DB.
The insurance assistant example
A pending approval is resumable without promoting a draft into an actual claim.
When to use it
Long-lived tasks and recovery across restarts.
When to avoid it
Avoid a single giant “memory” collection for messages, approvals, claim truth, and checkpoints.
Interview answer
“I separate execution checkpoints, user memory, and authoritative business records because their ownership and retention differ.”
Benefits, trade-offs, and production considerations
- Plan consistency and migration between these stores.
- The UI should show claim receipt data from the authoritative service, while run records explain how the assistant reached it.
Can you explain it without the notes?
State persistence and checkpoints
Use your own words. Explain an example and one limitation before checking the explanation.
Check your explanation
State persistence stores task progress; checkpoints record recovery positions. Neither automatically means user preference memory. A durable claim workflow may need execution records even when conversational history is deleted under a different retention…
Turn this concept into a clear answer.
Practice this conceptAdapted from 13_AI.MD · “State persistence and checkpoints”. Examples are study fragments; framework behavior can depend on your version.