Skip to main content

ActivityLimit

Use this setting to increase the number of activities in a single pipeline to up to 80, enabling more parallel calls, especially beneficial for batch pipelines. This enhancement helps optimize performance and efficiency by allowing more concurrent activities within a single data processing workflow.

When to Change This Setting​

Azure Data Factory pipelines have a hard limit of 80 activities per pipeline. BimlFlex uses this setting to split large batches into multiple sub-pipelines when the activity count would exceed the limit. The default (40) is conservative — increase toward 80 if your pipelines are simple (fewer nested activities per object), decrease if you see ADF deployment errors about activity limits. If your batch has 200 objects each generating 2 activities, a limit of 40 produces 10 sub-pipelines; a limit of 80 produces 5.

Notes:

  • This setting is part of the Azure settings category.
  • The default value for this setting is 40.