Interpret platform-limit risk, large workflow warnings, request-volume estimates, and child-flow dependency signals.
Large Nintex workflows can run into Power Automate action, nesting, switch, variable, run-duration, request-volume, and packaging limits. These guides explain what Flow Migrator detects and what to do when a risk is flagged.
Articles in this category
Browse all guides in Power Automate limits.
Refactor solution package for oversized workflows
Learn when to use the refactor solution package for Nintex workflows that exceed Power Automate action, nesting, or variable limits.
How Flow Migrator helps fix workflows that exceed Power Automate limits
Use this guide when a Nintex workflow is too large, too deeply nested, or too variable-heavy for a normal single-flow Power Automate export.
How SourceItem and MigrationContext work in refactor packages
Understand how Flow Migrator passes source-item data and shared workflow state between parent and child flows in a refactor solution package.
Use variable optimization in Optional settings
Learn when Flow Migrator should consolidate safe initialized variables into one object variable and when to preserve the original variable actions.
How to read the Power Automate limit-risk panel
Understand the platform-limit risk cards for actions, nesting, variables, expressions, URLs, approvals, loops, connector volume, and packaging.
Why detected source steps differ from estimated Power Automate actions
Learn why the Analyze coverage count can be higher than the emitted Power Automate action estimate.
How large workflows, child flows, and nesting are scored
Understand the risk signals Flow Migrator uses for 500-action workflows, 8-level nesting, child workflow dependencies, and solution packaging.