Description
Creating 1 parent machine and 2 children is making the viz create the 3 machines independently (without parent) first and then creating a new instance of the first child called from the parent but with this last one not being interactive. The viz shows the first child instance (without parent) but when viewing the invoked one (via Actors tab) such state chart cannot be interacted with.

Expected Result
When creating a child machine and then invoking it from the parent, the same child machine instance should be used and it should be possible to interact with it.

Actual Result
When creating a child machine and then invoking it from the parent, a new child machine instance is created and it's not possible to interact with it.

Reproduction

Given 2 children machines(authNavigationStateMachine and appNavStateMachine) and one parent appRuntimeStateMachine that invokes authNavigationStateMachine on init, the "Actors" tab shows 4, with the authNavigationStateMachine apparently duplicated:

-> authNavigationStateMachine (x:57)
-> appNavStateMachine (x:58)
-> appRuntimeStateMachine (x:59)
-> appRuntimeStateMachine (x:59) → authNavigationStateMachine (x:61)

the viz shows authNavigationStateMachine (x:57) which is not the one invoked by appRuntimeStateMachine (x:59) so when clicking the event that transitions to the authNavigationStateMachine final state it doesn't get back to the parent.

Going to the "Actors" tab and clicking on "-> appRuntimeStateMachine (x:59) → authNavigationStateMachine (x:61)" shows the authNavigationStateMachine but clicking on any event doesn't work.

Additional context

Link to the viz file.

https://stately.ai/viz/dcd508c8-0915-4c3f-9ad3-d881a1f37d0f#