Critical bug with Figma Slots — nested instances and parent components

Hi Figma Support Team!

We’ve encountered a critical issue with Slots in Figma that is significantly impacting our design workflow and slowing down development.

Issue description
When working with nested component instances inside Slots, modifying the contents of a slot can cause unexpected changes to other nested instances of the same component and even affect the original Main Component. Slot contents can be altered or broken unexpectedly, and parent component properties may stop propagating to nested instances.

Steps to reproduce

The issue occurs regularly in our workflow, although it may not reproduce on the first attempt.

Current workaround
Resetting the affected instance appears to restore the expected state. However, the issue reoccurs when duplicating the component and repeating the same workflow. This workaround is unreliable, especially in large design files where unintended changes or resets can easily go unnoticed.

Impact and urgency
Our design system relies heavily on nested components and Slots. This issue creates a significant risk of unintended changes to shared components and existing designs, making it difficult to maintain consistency and safely continue development.
Multiple teams within our company have encountered the same issue, suggesting that this is not an isolated case.
We’ve found two related discussions on the Figma Community Forum:

Could you please investigate this issue as a high priority and let us know whether it’s a known bug and if a fix is planned?
We can provide a sample file and screen recording demonstrating the behavior to help your team reproduce the issue.

Thank you in advance!