Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I see this as a current limitation (total 80 per pipeline). If I am calling forEach for an array length of 15 and forEach has 6 inner activities, is that deemed to fail due to reaching limitation?
starting activities (3) + (15 x 6) = 93? or is it considered as a total 4 activities.
If the total count is 83 for this pipeline that it will reach the limit and it will error out.
In that case, can i break this into 2 different pipelines (P1 and P2 by splitting the array) and invoke them in a different pipelne P3 and that would be considers as a total of 2 activities and it will be well below the limit?
Thank you in advance.
Solved! Go to Solution.
So it is 4 outer activities + 6inner activities.
So total count is 10 activities
Hi @smpa01
Thank you very much NandanHegde for your prompt reply.
Can you tell me if your problem is solved? If yes, please accept it as solution.
Regards,
Nono Chen
The limitation is w.r.t the number of activities present while publishing the pipeline.
Not the number of executions.
You can have more than 500 iterations etc
So, in the current pipeline screenshot, it would be considered as 4 activities ?
So it is 4 outer activities + 6inner activities.
So total count is 10 activities
It is basically the activities that you drag and drop within the pipeline
@NandanHegde thank you very much for this. I have a follow up questions to this.
1. If I split up my current array of 20 to 8 +12 (each containing 10 activities - as per your explanation) and build two seperate pipelines called P1 and P2 and create a seperate pipeline P3 and invoke p1 and P2 in P3; will it be considered as 2 activities or 10 activities.
Invoke pipeline activity is considered as a single activity count within the pipeline. The number of activities within the another pipeline which is being triggered is not considered within the pipeline via which the pipeline is being triggered.
Also data pipelines at the end are basically json codes, so in case if you are familiar with the framework you can code from backend rather than drag drop