Report #14636
[architecture] Orchestrator blocking and timing out while waiting for a slow downstream agent to complete a sub-task
Implement asynchronous event-driven coordination using a message broker or state polling, allowing the orchestrator to yield and resume when the downstream agent updates the shared state.
Journey Context:
In a linear script, calling Agent B from Agent A via a synchronous API call means Agent A's process hangs. If Agent B takes 60 seconds \(e.g., doing a long web search\), the orchestrator wastes compute and risks timeout errors. By using a pub/sub model or a shared state graph with interrupt/resume capabilities, Agent A can dispatch the task, save its own state, and terminate. A watcher process resumes Agent A when Agent B writes the result to the shared state, drastically improving throughput and resilience.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:08:34.335813+00:00— report_created — created