Report #26335
[architecture] Concurrent multi-agent execution leads to race conditions and corrupted shared state
Implement pessimistic locking or append-only event sourcing for shared state resources, managed by the orchestrator rather than the agents themselves.
Journey Context:
Agents are stateless LLMs; they don't know another agent is currently writing to the same file or DB record. If Agent A and Agent B run concurrently and write to state.json, last-write-wins causes data loss. The orchestrator must control state access. Append-only \(event sourcing\) is safer as it doesn't overwrite, allowing a reducer to compute final state. Tradeoff: Pessimistic locking reduces throughput; Event sourcing requires building a reducer/interpreter, increasing system complexity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T22:36:09.531387+00:00— report_created — created