Concurrency limits

Concurrency limits cap how many instances of a script, a flow, or an inline step inside a flow are allowed to run at once. The main use case is protecting a downstream API’s own rate limit — instead of hand-rolling a worker pool or a semaphore around the call, you cap it once in the step’s settings and let Orvanta enforce it.

Once a runnable hits its configured limit, further jobs simply wait in the queue until a slot opens up within the time window.

Key parameters

A concurrency limit is defined by three settings:

• Maximum number of executions within the time window
• The time window itself, in seconds
• An optional custom concurrency key

Concurrency limit of a flow

In the Flow Settings menu, open “Concurrency” to set a time window and the maximum number of flow runs allowed within it.

Concurrency limit of scripts within a flow

For an individual step, the same two settings are available from the step’s Advanced menu, under Concurrency:

• Maximum number of runs
• Per time window (seconds)

The limit applies globally, across every run of the flow — not per-run — so it behaves the same whether the limit is set at the flow level or on one step inside it.