How to fix self runAfter errors on import
A self runAfter error means one action's dependency list points back to the same action name. That usually happens after scope flattening, renaming, or branch merging has changed the final action keys without updating every dependency safely.
Why the error appears
Power Automate validates runAfter strictly. If an action says it depends on itself, import fails immediately. This is normally caused by a generator issue in the exported definition, not by the original Nintex logic.
The risk goes up when trivial wrapper scopes are flattened and a child action inherits the same final name as the wrapper or one of its siblings.
The 'runAfter' property of template action 'Compose' is not valid. The action cannot be itself.
What a healthy export pass should do
The exporter should flatten only safe wrappers, then rebuild dependencies against the final action names. A preflight pass should also scan for self-references and missing dependency targets before the ZIP is finalized.
If the export review catches the issue early, the user never sees the Power Automate import error in the first place.
What to do next
Re-export after the generator fix rather than editing the package manually. If the error persists, compare the failing action to the branch structure around it. Most self runAfter issues come from one localized flattening or dedupe path.
Treat this as a packaging defect to be corrected centrally, not as a sign that the workflow is fundamentally unsupported.