Report #92391
[architecture] Blocking the main orchestrator while waiting for a sub-agent to complete a long-running task
Dispatch sub-agents asynchronously and use an event-driven architecture or polling mechanism to check status, keeping the orchestrator free to handle other inputs.
Journey Context:
If Agent A calls Agent B \(e.g., to run a long code execution or web scrape\) and blocks, the system is deadlocked for the user. Multi-agent systems must treat sub-agent execution like microservices: fire off the task with a correlation ID, and process the result via a callback or polling when the state changes. This requires a persistent state store for the orchestrator but prevents timeout failures and unresponsive systems.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:40:09.280559+00:00— report_created — created