New Member

Solved

Critical bug with Figma Slots — nested instances and parent components

9 replies
379 views

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

Open a component that contains nested component instances inside Slots.
Duplicate a child component instance.
Start modifying the items inside its Slots.
Observe that the changes can unexpectedly affect other child instances and/or the original Main Component.

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:

https://forum.figma.com/report-a-problem-6/fix-slots-52242
https://forum.figma.com/report-a-problem-6/figma-slots-nested-instance-overrides-break-parent-properties-52740

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!

Ivan_DevlikamovSolution

New Member

Hi Figma Team @Celine_, @Jaycee Lewis!

Thanks for following up and looking into this issue.

The issue is no longer occurring for now. I recently rebuilt the affected interface, including the nested components and Slots, and everything has been working as expected since then.

However, I can’t say for certain that the issue has been permanently resolved, as it may still reappear. For now, I haven’t encountered it again and haven’t been able to reproduce it.

I’ll keep an eye on it and will reach out if the issue comes back.

Thanks for your help!
Best,
Ivan

Alexey Shamal

New Member

Bump! Same problem with slots

Jaycee Lewis

Figmate

Hi @Ivan_Devlikamov 👋 Thanks for flagging this. I opened a support ticket for this. The ID is 2207519 and the email subject line is Editing nested Slot contents affects other instances and main components. I added a few requests to the ticket.

Please keep an eye on your email (and spam folder if necessary) for the email and any replies from our team. Thank you! — Jaycee

Vlad_Altenar

New Member

Same problem!

Magnus_Wikensten_IPEX

New Member

@Jaycee Lewis What is the status on this ticket 2207519? I experienced this bug today in my Figma which is up to date, and was super time confusing to understand what was happening :( The Figma AI agent managed to guess it was the slot instance that creates this unexpected behaviour. Thanks.

Celine_

Community Support

Hey @Magnus_Wikensten_IPEX , Celine from the Figma Community Support team here, stepping in for @Jaycee Lewis . Thanks for sharing that you’re seeing similar behavior and sorry to hear this!

The investigation linked to 2207519 is still waiting on additional information from the original reporter.

I’ve gone ahead and created a separate support ticket on your behalf so our support team can investigate your example too. Please reply to the support email with the affected file link and, if possible, a short recording showing the unexpected changes. Grant Can View access to support-share@figma.com, and keep those details in the private support conversation. For reference, your case number is 2256545, sent to your email address: exxxl.mxxs.lxxxxn@ixxr.ixxxa.xxm, thank you!

Ivan_DevlikamovAuthorSolution

New Member

Hi Figma Team @Celine_, @Jaycee Lewis!

Thanks for following up and looking into this issue.

The issue is no longer occurring for now. I recently rebuilt the affected interface, including the nested components and Slots, and everything has been working as expected since then.

However, I can’t say for certain that the issue has been permanently resolved, as it may still reappear. For now, I haven’t encountered it again and haven’t been able to reproduce it.

I’ll keep an eye on it and will reach out if the issue comes back.

Thanks for your help!
Best,
Ivan

Celine_

Community Support

Great to hear everything is working again, Ivan! Thanks for the update. If the issue comes back, feel free to reply directly to your existing support case, and it will automatically reopen. I'll go ahead and mark this Forum thread as solved. 🙂

For anyone else experiencing a similar issue, we recommend submitting a bug report directly to our support team so they can investigate your specific case and provide further assistance.

To do that: Go to the Support Hub / Type “Report a bug” / Click Start a chat and select Enter and follow the prompts.
In the form, include the URL of the file and grant "Can View" access with support-share@figma.com This allows us to reproduce the issue and investigate, thank you!

Lucas West-

New Participant

Hi @Ivan_Devlikamov , @Celine_ , @Jaycee Lewis ,

I’m hitting what looks like the same bug as of this moment, on Windows Desktop 126.11.8, and I have steps that reproduce it every time, which might be the missing information for case 2207519. This problem remains absolutely critical to me and my projects and is still present.

The trigger in my file is a variant change on an instance that has a slot below it. After that, slot content inherited from the component stops being separate per instance: an edit to it lands in the main component and shows in every other instance. Before the variant change, the same edit behaves correctly.

That may also be why rebuilding made it go away for now. In my file, freshly placed or copy-pasted content behaves correctly until the next variant change above the slot.

Full steps, screenshots and Plugin API data are in my thread: https://forum.figma.com/report-a-problem-6/critical-slot-back-propagation-after-a-variant-change-above-a-slot-inherited-slot-content-is-shared-between-instances-and-the-main-component-editor-and-prototype-reproducible-steps-60046. The file itself is shared with support through my tickets. My tickets are #2213849 (editor) and #2259763 (the same thing in prototypes).

Ivan, if it comes back, it would help to know whether a variant had been changed on the component containing the slot just before.

ksn

Community Support

Hey @Lucas West- just wanted to pop into your reply and let you know I’ve given an update over on your topic here:

Please use that topic to relay any other issues or notes related to your slots problem -- that way, I can make sure your information stays connected in one place. Thank you!

Sign up

Login with SSO

Login to the community

Login with SSO