Thank you very much for reporting this issue. It seems that GetFSMActiveState returns only the FSMs that are launched by the specified object. However, while SubFSM runs in the same context object as ParentFSM, it is actually launched by the ParentFSM itself. This is necessary so that ParentFSM can properly stop SubFSM when SuperState1 is exited. However, this prevents GetFSMActiveState from finding SubFSM as you would expect. It seems that I did not approach this use case properly. Unfortunately, there is currently no way to retrieve the SubFSM instance in this scenario. I am currently working on a fix. Please stay tuned.