Checkpoints, persistence, and memory
Words made simple
A few useful meanings before you read the explanation.
- 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.
- State
- The data describing where a workflow is now, what it already knows, and what still needs to happen.
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.
- Tenant
- A customer or organization whose data must stay separate from other customers in a shared application.
- HTTP
- The request-and-response protocol used on the web. HTTPS adds encryption to protect information in transit.
Overview
- A checkpoint records execution progress and state at a recovery boundary.
- Persistence saves it outside the process.
- Memory is selected information reused by later turns or tasks; a checkpoint is not automatically good long-term user memory.
Why this matters
Users return later, workers restart, and approvals may take hours.
An everyday example
Save your position in a case checklist; a customer profile is a different record.
A technical example
Persist graph checkpoints in a supported database backend; store approved language preference separately.
How it works
- Execute step
- Checkpoint state/progress
- Associate with authorized thread
- Load on continuation
- Resume compatible graph version.
Architecture and flow
Graph runtime ↔ durable checkpoint store; context builder ↔ scoped memory store.
The insurance assistant example
A customer confirms a claim draft tomorrow without starting document collection again.
When to use it
Stateful conversations, approvals, and recoverable multi-step runs.
When to avoid it
Do not use process-memory checkpoints for production durability or assume persisted history should all be sent to the model.
Interview answer
“Checkpoints recover execution; long-term memory supports selected continuity. I isolate them and enforce thread ownership and retention.”
Benefits, trade-offs, and production considerations
- Back up checkpoint stores, encrypt sensitive data, serialize updates for the same thread, and plan graph migrations.
- Index tenant/thread ownership separately.
- Checkpoint persistence does not make database writes and external calls one atomic transaction.
- LangGraph persistence.
Can you explain it without the notes?
Checkpoints, persistence, and memory
Use your own words. Explain an example and one limitation before checking the explanation.
Check your explanation
A checkpoint records execution progress and state at a recovery boundary. Persistence saves it outside the process. Memory is selected information reused by later turns or tasks; a checkpoint is not automatically good long-term user memory.
Turn this concept into a clear answer.
Practice this conceptAdapted from 13_AI.MD · “Checkpoints, persistence, and memory”. Examples are study fragments; framework behavior can depend on your version.