Concurrent write bugs silently corrupt shared agent state
A post by u/mrvladp describes two silent data-loss failure modes in multi-agent systems — concurrent lost updates and zombie writers — and presents a purpose-built coordination layer to prevent them.
Score breakdown
Silent write collisions in shared agent state cause data loss that gets misattributed to model errors, and this post demonstrates that both failure modes can pass all version checks and produce clean-looking runs — making them particularly difficult to detect without purpose-built concurrency controls.
- 01Two failure modes described: concurrent lost updates and zombie writers, both producing silent data loss in multi-agent systems.
- 02In a lost update, two parallel workers write to the same key simultaneously; both return success but one write is silently dropped.
- 03The data gap typically surfaces several steps later as apparent model forgetfulness, not as an immediate error.
u/mrvladp on r/AI_Agents identifies two failure modes that plague multi-agent orchestrators sharing state — such as a memory store, decisions document, or plan file — and that are routinely misattributed to the model. In the first, the concurrent lost update, a planner dispatches multiple parallel workers that each write results to a shared key. When two finish simultaneously, both writes return success, but only one survives. Because no subsequent agent re-reads the artifact with suspicion, the next prompt silently inherits the truncated state, reasons over it fluently, and the missing data only surfaces several steps later as apparent model error. In the second, the zombie writer, a long-running agent stalls while holding a write grant. Recovery correctly reclaims the grant to unblock the rest of the fleet, but the stalled process later wakes up and completes its write. If nothing else modified the artifact in the interim, the version number still matches, every version check passes, and the stale commit lands on top of state the system has already moved past.
The post describes a coordination layer built to address both problems.
The post describes a coordination layer built to address both problems. Concurrent same-key writers resolve to exactly one winner; the loser receives a typed, retryable conflict error instructing it to read fresh state, recompute, and commit again — rather than silently dropping the write. Zombie writes are blocked through ownership epoch fencing: every reclamation increments an epoch, every write claim records the epoch it was made under, and the commit checks both atomically alongside the version persist, rejecting any write whose epoch no longer matches. The guarantees are model-checked in TLA+, with the checker running in CI; each spec includes a documented mutant — deleting the guard — that must turn the checker red, ensuring every invariant is genuinely load-bearing. The tool runs over plain files shared across processes and ships with adapters for LangGraph, CrewAI, AutoGen, and the OpenAI Agents SDK. The post notes the scope is limited to a single coordinator and single host, with cross-host support not yet built.
Key facts
- 01Two failure modes described: concurrent lost updates and zombie writers, both producing silent data loss in multi-agent systems.
- 02In a lost update, two parallel workers write to the same key simultaneously; both return success but one write is silently dropped.
- 03The data gap typically surfaces several steps later as apparent model forgetfulness, not as an immediate error.
- 04In a zombie writer scenario, a stalled agent's write grant is reclaimed for recovery, but the process later wakes and commits stale state — passing version checks because nothing else modified the artifact.
- 05The coordination layer gives the losing writer a typed, retryable conflict error instead of a silent drop.
- 06Ownership epoch fencing rejects zombie writes: every reclamation bumps an epoch, and commits check the epoch atomically with the version persist.
- 07TLA+ model-checked guarantees run in CI; adapters exist for LangGraph, CrewAI, AutoGen, and the OpenAI Agents SDK; cross-host support is not built.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 11, 2026 · 08:34 UTC. How this works →