How to read the Power Automate limit-risk panel

What the panel is measuring

The panel combines import-time risks and runtime review signals. Import-time risks are limits that can stop a generated package from importing cleanly, such as emitted action count, generated nesting depth, Switch case count, variable count, expression length, and URL length.

Runtime review signals are not always blockers. They help migration teams identify workflows that may need extra design validation because they use approvals, delays, loops, connectors inside loops, child workflows, or payload-heavy actions.

• OK means no immediate limit concern was detected for that metric.
• Warning means the workflow should be reviewed before export or before a pilot import.
• High means the workflow is likely to need design validation, splitting, or a careful test plan.
• Blocker means the generated flow may exceed a Power Automate platform limit unless it is refactored.

The most important cards

Estimated Power Automate actions is the card most closely tied to the cloud-flow action limit. It estimates the number of emitted Power Automate actions after analyzer-only branch and case rows are removed.

Generated nesting depth is measured from the Power Automate draft. Source depth is shown for context and does not block export. If required settings prevent draft generation, output depth is pending until the configured output can be measured. Child workflow dependencies identify callable or reusable workflows that need a parent/child strategy.

• Action estimate over 500 is a blocker-level design risk.
• Nesting above 8 is a blocker-level source-design risk even if generation can flatten part of the workflow.
• Variable count warnings should be reviewed alongside the Optional settings variable-optimization option.
• Switch/state branch counts above 25 need branch splitting or a different dispatch pattern.
• Run-duration and request-volume risks are planning signals for validation, monitoring, and licensing discussions.

How to use the panel in a customer assessment

1. Review the coverage counts first to understand supported, partial, and unsupported source steps.
2. Open the Power Automate limit-risk panel and identify any Blocker or High cards.
3. For blocker-level action count or nesting, decide whether the workflow should be split before export.
4. For runtime risks, include extra validation tasks in the pilot plan instead of treating the workflow as a simple conversion.
5. Download the branded PDF report so the customer can review the risk profile with workflow owners and Power Platform admins.