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
- Alex Townsend posts 200 open problems in numerical linear algebra for humans and AI agents — IgorCarron · 2026-09-11
- Kimi K2.8 Preview rolls out: near-K3 coding performance, 1M context for all tiers — teortaxesTex · 2026-09-11
- Looking for a classifier of software engineering task shapes to pick models per task — StewartalsopIII · 2026-09-11
- Steal this idea: prompt-to-hardware where agents assemble custom devices — paraschopra · 2026-09-11
- Model Is the Least Interesting Part: A Guide to Six Core AI Architectures from RAG to Multi-Agent — goyalshaliniuk · 2026-09-11
- Non-coder builds layered memory architecture: 20k tokens tracks a year of agent conversations — matteoianni · 2026-09-11