Batch trigger concurrency limits increased across Free and Pro tiers
Developers can process more background jobs simultaneously, with concurrency limits bumped from one to five for Free accounts and ten to fifty for Pro accounts.
Higher concurrency limits allow developers to process more background jobs simultaneously without hitting rate limits or queueing delays.
The official documentation has been updated to reflect a capacity boost for both Free and Pro tier users. Free accounts can now execute five concurrent batches, up from a strict limit of just one. Meanwhile, Pro accounts see their capacity expanded from ten to fifty concurrent batches.
This change applies specifically to the platform's batch triggering system, where a single batch request is fanned out into individual runs. The documentation now correctly reflects these higher numbers in the .