Export & import
Generate cleaner packages, fix common import failures, and understand what preflight is checking.
If a package downloads but fails to import, the error is usually specific and fixable. These guides cover the import errors users hit most often.
Articles in Export & import
Read the full set, or start with the featured guides if you are new to this topic.
How to generate and import your first package
Use Analyze and Required settings to reduce surprises, then validate the imported package in Power Automate before calling the migration done.
How to fix duplicate action name errors on import
Resolve 'The template action names must be unique' errors by re-exporting after the naming review pass and checking deep branches for collisions.
How to fix nesting-limit errors on import
Power Automate allows up to eight levels of nested actions; trivial wrapper scopes often need to be flattened before export.
How to fix self runAfter errors on import
Resolve 'The action cannot be itself' errors by checking flattened wrapper scopes and repaired action dependencies.
How to fix 'Required settings incomplete' export errors
If export still says a list or library is missing, the problem is usually stale analysis data or reference-name mismatch, not the idea of the site URL itself.
Search the knowledge base
Search across all categories if this topic is close, but not quite the right fit.
All categories
Start here
These guides usually answer the first two or three questions users ask in this category.
Recently updated in this category
Need a real workflow reviewed?
Public articles are great for recurring patterns. If you have a workflow export and want advice on the exact blockers, contact us with the workflow and the Analyze report.