Cloudflare is overhauling its Workflows control plane, a move necessitated by the dramatic shift from human-initiated tasks to the relentless pace of AI agents. Originally designed for user actions like sign-ups, Workflows now must handle persistent, autonomous agents operating at machine speed. This evolution demands a more robust, asynchronous execution engine capable of managing thousands of instances concurrently.
The company is now supporting 50,000 concurrent workflow instances, up from 4,500, and can create 300 instances per second per account, a threefold increase from the prior 100. Millions of queued instances are also now supported. This scaling is achieved through a redesigned control plane, moving from a single Durable Object bottleneck to a horizontally scalable architecture.
The Agentic Shift
The rise of persistent AI agents, which operate on behalf of users for extended periods, requires a durable execution engine. Workflows provides this by ensuring each step is independently retryable, allowing for human-in-the-loop approvals, and surviving failures without losing progress. Developers are increasingly using Workflows to build agent loops and manage their lifecycle.
Cloudflare's Agents SDK integration has further accelerated this trend, allowing agents to easily spawn workflow instances and retrieve real-time progress. A single agent session can now initiate dozens of workflows, and with multiple agents running, thousands of instances can be created in mere seconds.
V1 Limitations and V2 Architecture
The original V1 control plane relied on a single account-level Durable Object to manage all workflows. This proved to be a bottleneck as customer usage scaled, leading to rate limits of 4,500 concurrent slots and 100 instance creations per 10 seconds.