Yes, thank you, it is "kind of duplicated" since someone can find the answer inside the thread you gave. I was not able to find that thread on my own, which makes it only _kind of_ duplicated.
I am sorry my question was somehow low level, because I am still new to TestStand, although I am working on it ;). My difficulty was, that I did not understand, that the execution I started with the engine command "Run" was forking giving me only access to the initial clone.
Basically the DisplayExecution callback informs the exterior LabView OI when a new Testsocket started an execution.
Since you get this execution as parameter in the callback VI, it is easy to retrieve the test socket index (RunState.TestSockets.MyIndex) from the sequence context of the its ForegroundThread.
In my opinion this is also best practice, because like this you can create testsocket user interfaces dynamically, by starting a new test socket UI every time the DisplayExecution callback is triggered.
I for example do this by starting a dynamically created frontpanel reference asynchronously as fire and forget (0x80) an supplying and retrieving control and indicator values by index.
