This GIF shows the issue in real time. The nested component interactions are still present, but are hidden/disabled when nested inside a parent component. Detaching the instance of the parent shows that the interactions are still there.

This has to be a bug, right?

Hey All, thank you for your feedback! 

To be transparent, I flagged this to our team and they confirmed that this is expected behavior. We don’t support interactive components inside of main components that are directly integrated into frames. 

The team is now aware of this feature request and will continue to monitor it for future consideration.

Please use the temporary solutions as suggested by the community within in this topic to initially troubleshoot your specific issue, but if you’d like additional help, please feel free to reach out to our support team directly here: Submit a ticket

For those of you struggling to understand the workarounds like I was... 

The simplest solution I found was to wrap the nested components that have the interactions in another frame.

 

Something else I just discovered for anyone not wanting to read 4 pages of valid complaints…

You can override some of the weirdness that seems to be present when it uses hidden interactions you specifically have removed from instances, you can set the interaction to just be None for that same interaction type.
 

This seemed to stop it from executing the child interaction every other click.

EDIT: Just kidding this worked randomly for a little but now it still just steps through each interaction on the child even though I removed it from the instance.