Applied AI
LangGraph checkpoints can change dictionary key types
Enum, UUID or date keys in agent state may return as strings after a checkpoint, changing lookup behavior.
November 17, 2026
An agent can remember a value and still lose the ability to find it. LangGraph issue #9490 reproduces Enum, UUID and date dictionary keys changing type through checkpoint serialization. In the example, an Enum key returns as its string value, so the next turn starts a second counter instead of incrementing the first. This is a state-schema hazard for long-lived agents.
Find typed keys in durable state
Search state definitions and reducer outputs for dictionaries keyed by Enum, UUID, date or datetime. Inspect the serialized and restored form with the exact checkpointer and library versions used in production. LangGraph's persistence guide makes checkpoints the durable thread state; a type mismatch there can recur on every resume, not just after a process restart.
Make a round-trip test part of the contract
Write a state value with each key type, checkpoint it, restore it and assert both key type and lookup result. Include multiple invocations, because the reported bug becomes visible when the next turn reads the saved state. A green first invocation is insufficient. Test migrations against existing checkpoints before deploying a serializer change.
Choose an explicit stable representation
If typed keys are not essential to the domain, encode them as deliberate strings at the application boundary and decode only where needed. Put the encoding rule in one place and version it. Do not silently coerce all keys during an incident; existing checkpoints may contain both representations, so first inventory and plan a safe migration.
Adovo’s view
Memory is an interface, not a pile of objects. A durable agent needs a schema it can read tomorrow in the same way it writes today. Type round trips belong in release tests whenever decisions depend on saved state.
