Workflows scales to 50k concurrent instances

Summary

Agent-triggered workflows now replace human-triggered patterns, requiring durable execution at scale; developers building persistent agents need platforms that survive thousands of concurrent instances without losing progress or hitting hard rate limits.

Why it matters

Agent-triggered workflows now replace human-triggered patterns, requiring durable execution at scale; developers building persistent agents need platforms that survive thousands of concurrent instances without losing progress or hitting hard rate limits.

Sources

1. 1.50,000 concurrent instances (number of workflow executions running in parallel), originally 4,500
2. 2.300 instances/second created per account, previously 100
3. 3.2 million queued instances (meaning instances that have been created or awoken and are waiting for a concurrency slot) per workflow, up from 1 million
4. 4.a single agent session can now kick off dozens of workflows, and many agents running concurrently means thousands of instances created in seconds
5. 5.every step is independently retryable, the workflow can pause for human-in-the-loop approval, and each instance survives failures without losing progress