Autonomous Event-Driven Multi-Agent Orchestration for Enterprise AI at Scale
Summary
This paper evaluates multi-agent orchestration architectures (DAG Plan and Execute, ReAct) at enterprise scales and introduces a Task Manager for continuous event-driven operation, showing improvements in latency and correctness.
View Cached Full Text
Cached at: 06/20/26, 02:35 PM
# Autonomous Event-Driven Multi-Agent Orchestration for Enterprise AI at Scale Source: [https://arxiv.org/abs/2606.20058](https://arxiv.org/abs/2606.20058) [View PDF](https://arxiv.org/pdf/2606.20058) > Abstract:Enterprise AI aims to move toward continuous event monitoring, detection, and action across specialist agents, yet existing multi\-agent systems largely assume discrete request\-response workflows and remain underexplored at enterprise scale\. We evaluate DAG Plan and Execute and ReAct across 208 production\-derived enterprise scenarios spanning Persona \(<10 agents\), Department \(20\-80\), and Enterprise \(200\) scales, and introduce a Task Manager for continuous operation via priority inference, related\-event merging, and preemption\. Results show that scale, not task complexity, dominates orchestration performance: both architectures perform well at small scale but degrade at enterprise scale as agent discovery noise becomes the primary bottleneck, with simple tasks degrading more sharply than complex ones\. DAG Plan and Execute offers higher precision and structured parallelization at smaller scales, but its higher overhead worsens at enterprise scale; ReAct is more robust by handling failures incrementally\. The Task Manager reduces high\-priority queue latency by 14\-75% and improves related\-event correctness by over 20 percentage points at enterprise scale\. ## Submission history From: Leonidas Raghav \[[view email](https://arxiv.org/show-email/97c58942/2606.20058)\] **\[v1\]**Thu, 18 Jun 2026 10:32:38 UTC \(2,801 KB\)
Similar Articles
Experimenting with a multi-agent system without leaders or messaging
The author details an experimental multi-agent orchestration framework using a directed acyclic graph (DAG), concentrating intelligence in planner and replanner components while keeping worker agents mechanical. They are seeking community feedback, benchmarks, and existing research to validate its practicality against conventional message-passing approaches.
Simple Multi-Agent Architecture Running Across Our Entire Org. Keeping everything in Loop.
This article describes a multi-agent architecture running at scale, using LangGraph, CrewAI, and Harbor to handle goal agents, task coordination, and secure access with tracing.
Anyone running AI agents in production with proper orchestration?
A developer asks for recommendations on production orchestration tools for multi-agent AI workflows with branching, retries, and human-in-the-loop approvals, as their current FastAPI-based solution has become unmaintainable.
Has anyone deployed a multi-agent AI employee in production?
A discussion about deploying multi-agent AI systems in production, where different agents handle planning, execution, communication, and project management, asking about real-world experiences and bottlenecks.
Most "multi-agent orchestration" is just a single agent calling a function. Stop rebranding function calls as agents.
The article critiques the overuse of the term 'multi-agent orchestration,' arguing that many implementations are simply single agents using function calls rather than true distributed systems. It highlights practical, production-tested patterns like sequential pipelines and human-in-the-loop workflows as alternatives to complex but ineffective architectures.