Nesting level for actions in Power Automate

Question

While designing an advanced Power Automate flow, I included several conditions inside a loop. 

Each condition contains additional nested branches such as "If-else", "Switch", and "Apply to each". 

As I continued building, the flow started to get slower and more difficult to manage. I’m now wondering if there’s a technical limit to how deeply actions can be nested within each other in Power Automate, and whether exceeding that limit could cause performance or execution issues.

Answer 1

Allowed nesting depth for actions in Power Automate

In Power Automate, you can nest actions (like loops, conditionals, and switches) up to a maximum depth of 8 levels.

This means you can have an action inside an action, and so on, but not beyond eight layers deep. If you go beyond this limit, the flow might not save, or it could fail to run.

Exceeding that limit could cause performance or execution issues?

To maintain good performance and readability, it’s recommended to

• Flatten the logic where possible or use child flows to offload complex or repetitive actions.
• Also, using fewer nested structures also helps make the flow easier to debug and update later.

Ref: Power Automate Limits and Configuration