Concurrency limits

The concurrency limits feature enables you to establish concurrency restrictions for scripts, flows, and inline scripts contained within flows. Its primary purpose is to help prevent exceeding API limits of target services, removing the necessity for complex workarounds involving worker groups.

When jobs reach the specified concurrency limit, they are automatically queued for execution at the next optimal available slot within the defined time window.

Key parameters

The concurrency limit operates globally across flow runs and involves three main parameters:

Max number of executions within the time window
Time window in seconds
Custom concurrency key

Concurrency limit of a flow

Within the Flow Settings menu, select “Concurrency” to define a time window and specify the maximum number of flow executions permitted within that time window.

Concurrency limit of scripts within a flow

For individual steps within a flow, concurrency limits can be configured through the Advanced menu on the Concurrency tab. The concurrency limit operates globally and across flow runs, with two primary parameters:

Maximum number of runs
Per time window (seconds)