Multi-agent systems fail less on reasoning than on orchestration, says one production team
njanChe1 · reddit · 2026-07-23
The hard part of multi-agent systems, the author argues, is not the agents themselves but failure handling when one worker dies mid-task.
- The post says most tutorials skip the real problem: workers OOM’ing, planners emitting impossible tasks, and races between results.
- What worked in production was treating orchestration as a distributed-systems problem:
- message bus plus durable queues
- typed task contracts
- an aggregator that waits on a pre-registered task set
- stateless, single-purpose workers that never call each other
- If a worker dies, its task simply remains on the queue.
- The key split is clear: the model decides what to do, while durable infrastructure guarantees it actually gets done.
The author asks what others are using for orchestration: custom code, LangGraph, Temporal, or something else.
Related event: Engineering Challenges Plague Multi-Agent Systems(3 posts)→
More from coding & agent
- Hugging Face wraps 6-month Training Agents series with open recordings and code — SergioPaniego · 2026-10-26
- Agent verified 'success' after double-voting: a lesson in harness vs model bugs — TejasKumar_ · 2026-10-26
- diginomica: agentic automation hype is overdone, and 'The Hackening' of enterprise security has begun — jonerp · 2026-10-26
- 'Vibe verification': ~60% of AI-written formal specs prove the wrong property — basedjensen · 2026-10-26
- Devin launches Security suite powered by Claude Mythos with $100M+ credits — DevinAI · 2026-10-26
- HackBench injects reward hacks into agent trajectories to stress-test monitors — DanielKhashabi · 2026-10-26