Report #77908
[architecture] Corrupted multi-agent state when one agent fails after another has committed side effects
Implement the Saga pattern: for every tool call that mutates state, define a compensating transaction \(undo action\), and have the orchestrator execute compensations if a downstream agent fails.
Journey Context:
If Agent A provisions a server and hands off to Agent B to configure it, but Agent B fails, the server is left orphaned. Developers try to use database-style distributed transactions, but external APIs don't support 2PC. The Saga pattern is the standard microservices solution adapted for agents: the orchestrator must catch the failure and invoke Agent A's compensating action \(deprovision\) to roll back the state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:21:48.682736+00:00— report_created — created