How do you solve for this? The power flow's logic app flow template was invalid. The template actions 'Create_item_4, Send_an_email_(V2)_7, Create_item_6' are nested at level '9' which exceeds the maximum nesting limit of '8'.

[joshcasa25]

Hi! I need help with this before Wednesday please! 

My logic is that after a sharepoint list item is created, an email is sent to the applicant, then after creating variables for the direct supervisor's approval and a variable (array) to account for multiple roles to be chosen and displayed within a teams adaptive json code, we trigger the adaptive card to appear, then we retrieve all the outcomes that are decided (i.e., direct supervisor's name, approval date, phone no., office location, etc.). After we check to see if the Direct Supervisor approves or rejects based on a condition focused on the Direct Supervisor's outcome. If they approve it, we update the item, then create a new item with the Direct Supervisor's retrieved information so that we can store multiple historical records on the sharepoint. We then enable a start and wait for an approval action for the 2nd approver, they input their information (i.e., name, date, outcome, comments), then we update the previous item with a change of status, and create a new item. We repeat this until we get to the final approver, wherein we create an item and send an email that the total approver process has been completed and approved. However, at the very last level (i.e., wherein the final approver condition is enabled), I exceed my nesting limit.  Can someone help me solve this please?

[joshcasa25]

Here are the additional screenshots

[joshcasa25]

@jaina , @SudeepGhatakNZ , would you all happen to know how to solve this? 

[joshcasa25]

@Expiscornovus , @Pstork1 would you all happen to know how to solve this? 

[Chriddle]

Did you knowingly insert all of these loops, or were they just inserted automatically?

[joshcasa25]

automatically. My hunch is that it did so automatically because I referencing information from previous "start and wait" actions. 

[Pstork1]

The only way to solve this is to decrease the number of nesting levels. To do that you will need to store some values in variables when you get to the 4th or 5th level of nesting. Then start over with those values in the main line of flow using a switch. Doing it that way you can get the logic you need and avoid the nested levels that are the issue.

[jaina]

Hi @joshcasa25 ,

As i noticed, the next approval action was inside another apply to each. Try to move it out.

Here's mine. I have 6 approval layers. In addition, instead of getting the values from previous approval action, get the appended variable.

1st - Initialize String Variable, named it '1st approver'

Next, in the condition action, append string variable to input the value from the 1st approval layer.

Next, outside the apply to each action, and under the same condition, add new approval action. In getting the value from 1st approval layer, you may capture the data from string instead of previous approval layer to avoid nested layers.

[Chriddle]

First of all I would check the inputs of each "Apply to each". Do you really need an array there?

For example, if such an array can only contain one element, you can retrieve that element with the function first() and continue without the loop.