how to fix The template validation failed: 'The number of template actions limit exceeded: maximum '1500' and actual '1501'

Question

how to fix The template validation failed: 'The number of template actions limit exceeded: maximum '1500' and actual '1501'

Goundla, Sai Karthik Goud 0

Error in ADF: Operation on target For Each Tenant failed: Activity failed because an inner activity failed; Inner activity name: Execute StageTenantTablesInner, Error: ErrorCode=InvalidTemplate, ErrorMessage=The template validation failed: 'The number of template actions limit exceeded: maximum '1500' and actual '1501'

Manoj Kumar Boyini 18,595 Reputation points Microsoft External Staff Moderator

2026-06-25T06:53:02.4366667+00:00

Hi @Goundla, Sai Karthik Goud

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

2 answers

Your answer

Manoj Kumar Boyini 18,595 Reputation points Microsoft External Staff Moderator

2026-06-25T06:53:02.4366667+00:00

Hi @Goundla, Sai Karthik Goud

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Answer 1

Manoj Kumar Boyini 18,595 Microsoft External Staff Moderator

Hi @Goundla, Sai Karthik Goud

This is typically caused by a large pipeline design containing a significant number of activities, nested containers (such as ForEach, If Condition, Switch, or Until), or repeated workflow patterns that result in the compiled pipeline exceeding the supported action limit.

In this case, the failure occurs within Execute StageTenantTablesInner while executing the For Each Tenant activity, indicating that the overall workflow has exceeded the maximum supported number of template actions.

To resolve the issue, consider refactoring the solution by:

Splitting the workload into multiple smaller child pipelines.

Reducing the number of activities executed within the ForEach loop.

Processing tenants or tables in smaller batches.

Consolidating repeated logic through parameterization and reusable pipeline patterns.

These approaches help reduce the total action count and keep the pipeline within the supported limits.

Please let us know if you need any further assistance.

References:

Azure Data Factory limits and quotas:
https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-data-factory-limits
ARM template limits and best practices:
https://learn.microsoft.com/azure/azure-resource-manager/templates/best-practices#template-limits

Goundla, Sai Karthik Goud 0 Reputation points

2026-06-25T07:35:24.68+00:00

I set up the main pipeline with a for loop that triggers stageinner1/stageinner2/stageinner3 with a batch size of 15, the same as before. Will this work now? Also, can I run all three in parallel, or do I need to add dependencies so each pipeline completes before the next one is triggered?
Manoj Kumar Boyini 18,595 Reputation points Microsoft External Staff Moderator

2026-06-25T07:44:30.0433333+00:00

@Goundla, Sai Karthik Goud

Yes, you can run stageinner1, stageinner2, and stageinner3 in parallel if there are no dependencies between them. If one stage depends on the output of another, they should be chained using dependencies and executed sequentially.

Also, reducing the workload into multiple child pipelines helps address the template action limit, but the final result depends on the overall compiled pipeline remaining within the supported action limits.
Goundla, Sai Karthik Goud 0 Reputation points

2026-06-25T07:55:54.51+00:00

there is no dependencies between them, so can i run the stageinner1, stageinner2, and stageinner3 in parallel and this is work? or still fail due to limit error
Manoj Kumar Boyini 18,595 Reputation points Microsoft External Staff Moderator

2026-06-25T11:34:45.54+00:00

Hi @Goundla, Sai Karthik Goud

If there are no dependencies between stageinner1, stageinner2, and stageinner3, then running them in parallel is supported.

However, whether the template limit error is resolved depends on the action count within each individual pipeline after the refactoring. The original error indicates that the compiled workflow exceeded the maximum supported template action limit (1500 actions).

By splitting the logic into multiple child pipelines, the action count is distributed across separate pipeline definitions, which typically helps avoid this limit. If each child pipeline remains below the supported limits, running them in parallel should work.

If the error persists after the refactoring, it would indicate that one or more of the child pipelines still exceeds the supported action limit and may require further decomposition or simplification.
Manoj Kumar Boyini 18,595 Reputation points Microsoft External Staff Moderator

2026-06-26T08:37:21.9633333+00:00

Hi @Goundla, Sai Karthik Goud

Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.

Answer 2

Senthil kumar 1,465

Hi @Goundla, Sai Karthik Goud

As of now Microsoft allowed max 1500 actions per pipeline so avoid execute in same pipeline. split your actions into 3 to 4 pipelines then execute your actions.

ex : one foreach execute all actions it will consume limits.

Thanks.

Goundla, Sai Karthik Goud 0 Reputation points

2026-06-23T07:06:09.8766667+00:00

so i need to split my inner pipeline into 3/4 pipeline?
Senthil kumar 1,465 Reputation points

2026-06-23T07:15:09.2866667+00:00

Yes correct.
Goundla, Sai Karthik Goud 0 Reputation points

2026-06-23T08:20:22.9266667+00:00

Hi Senthil, can i know how this template actions limit is calculated
Senthil kumar 1,465 Reputation points

2026-06-23T09:36:39.51+00:00

This is a hard ARM template limit inherited from Azure Logic Apps.