How to track child workflow dependencies in Analyze
Nintex Start workflow actions often show a generic label in the source designer, but the target workflow name is stored inside the action configuration. Flow Migrator uses that target to make parent/child dependencies visible before export.
6 min readUpdated May 22, 2026child workflowsdependenciesStart workflow
Quick answer
In shortUnderstand child workflow call counts, unique reusable child workflows, and why Start workflow rows now show their target names.
Most likely causeA source workflow may display several steps named Start workflow. That is not useful during migration because the workflow owner needs to know which child flow each step is trying to call.
What to do nextReview the converted approval or task after import and validate assignees, responses, and follow-up branches.
Why Start workflow rows now include a target name
A source workflow may display several steps named Start workflow. That is not useful during migration because the workflow owner needs to know which child flow each step is trying to call.
Flow Migrator extracts the target workflow name from the Nintex configuration when it is available and displays it as part of the Analyze row title.
Start workflow: Create New Training Material Error Fix Item
How repeated child workflows are summarized
The Power Automate limits panel shows how many child workflow calls were detected and how many unique child workflow targets those calls represent. This matters because one shared child workflow may be called by many parent workflows.
In the report, repeated targets are grouped so migration teams can see whether they should package a shared child once or create isolated child flows for different business areas.
Use the total call count to understand dependency volume.
Use the unique target count to plan reusable child flows.
Use the step numbers to find each parent call in the source workflow.
What to do before export
Confirm that every child workflow export is available for the same migration wave.
Decide whether repeated child workflows should be converted once or duplicated intentionally.
Validate connection references so parent and child flows use consistent connectors in the destination environment.
Use a parent/child solution package or wave-based packaging strategy for complex chains.
Child workflow calls stay partial until the target child flow is created, imported, and wired in the customer environment.
Related articles
Keep reading the next most relevant guides for this workflow pattern.
