Trigger Child Flows 30+ Times: What are the limits of Child Flow runs?

[kudorje]

Use case: Our company has 55 systems where each system has a designated owner who is in charge of adding/removing permissions to a user. Therefore when a user wants to add/remove themselves to any or all of these 55 systems (via a SharePoint item entry), I want a parent workflow to realize which of the 55 systems were selected as "needs access" and then via a loop trigger a child workflow X times for each of the selected workflow. Where the child flow sends a Send email with Options where system owner is expected to complete their task and confirm back via the email that they are done with their task. For each approver upon approval/rejection, it is expected to update the SharePoint list item's system status. 

Additionally, the parent workflow is expected to trigger another workflow that monitors the status all columns of SharePoint item that were marked as access/remove needed and if their status has been approved/rejected. So basically if all haven't been completed yet, then don't proceed with the rest of the flow on that "referee flow". 

The reason why i am thinking of child flow is that all the systems have the same pattern. (either approve/reject). Its just the content of the approval request in the email that i need to change. So the child flow will do a lookup against a list that has a matrix of approvers and email body for each system based on the info sent over by the parent flow.

Question: Can Power Automate handle a request where there is the possibility of user selecting at least 30+ systems? I am specifically thinking about throttling and any other limits that may be there?

[DarmonGill]

Hi,

Yes, Power Automate can handle requests where there is the possibility of the user selecting at least 30+ systems.
However, there are some limits to consider when using Power Automate
The number of systems that can be selected depends on the performance profile of your flow .
The performance profile determines the Power Platform request limits for your flow.
The following table describes the plans that are associated with each of the four performance profiles:

Performance Profile Plans
Low Free, Microsoft 365 plans, Power Apps Plan 1, Per App plans, Power Automate Plan 1, All license trials, Dynamics 365 Team Member, Microsoft Power Apps for Developer
Medium Power Apps triggered flows, manual flows, child flows, Power Apps Plan 2, Power Apps per user plan, Power Automate Plan 2, Power Automate Premium (previously Power Automate per user), Power Automate Premium plans (previously Power Automate per user with Attended RPA plans), Dynamics 365 Enterprise plans, Dynamics 365 Professional plans, Dynamics 365 non-licensed users, application users, users with special free licenses
High Power Automate Process plan, Power Automate per flow plan, Unlimited
Extended Pay-as-you-go flows, Dynamics in context flows running under service principal
If a user has multiple plans, such as a Microsoft 365 plan and a Dynamics 365 plan,
the flow has the performance profile of the higher of the plans .

The Power Automate service typically allows higher counts than those documented in the performance profiles
and won’t slow flows down based on occasional and reasonable overages.
However, if your flow’s action count exceeds these limits, they are subject to potential throttling,or in cases of extended violations, disabled.

Gill

[kudorje]

The plan i show under my profile is "Power Automate for PowerApps Per User Plan". Does this fit under the medium?

[DarmonGill]

Hi,

The plan you show under your profile is “Power Automate for PowerApps Per User Plan” which fits under the medium performance profile 1. However, if your flow’s action count exceeds the limits, they are subject to potential throttling, or in cases of extended violations, disabled

Gill

[kudorje]

Can the limit be extended by the admins? In our case, we have PowerAutomate about 14 - 17 Flows that run on an given day. Each Flow can be triggered X amount times during the day. Now with this new workflow where the pattern is expected to run 30+ times, I am wondering if this can be reviewed by our admin and have the limit extended. Any ideas? I am in one of the downstream business groups and have no access to admin controls.