Figma Slots Bug - Instances containing slot(s) don't receive the same updates as their main component

We have currently the same issue! 

Hey ​@Iasonas Georgiadis 👋 Thanks for the clear write-up — the "some instances update, some don't" part helps narrow this down, so I appreciate you calling it out.

To dig into the inconsistency, a few things would help for you or ​@Lara9 (or both 😊):

• A short, full-screen screen recording showing the main component edit and an instance that fails to pick it up. Seeing it happen is the fastest way for us to pin down the cause.

• Are these components coming from a published library? When an update doesn't propagate, are you editing in the library file itself or in a file that uses it?

• On an instance that doesn't update, click into it and check the right sidebar—is the whole slot showing as overridden, or just specific container properties?

That third point is worth noting — slot overrides can have a wider scope than expected, catching properties you think are outside the slot.

To test this: 

• Change a parent property like fill or corner radius on a fresh instance's main component
• If it updates, configure the slot and change that property again
• If it stops updating, the override scope is the culprit

Thanks for the additional information! — Jaycee

Hi Jaycee,

A short, full-screen screen recording showing the main component edit and an instance that fails to pick it up. Seeing it happen is the fastest way for us to pin down the cause.

I’ve attached two videos for reference.

In the first video, you can see that configuration does not work correctly on a heavily configured component. In the second video, however, everything appears to work as expected—at least when creating a fresh instance and editing it directly.

This makes me wonder whether the issue is related to the complexity of the component configuration or if there is another limitation at play

Worth mentioning that everything seem to work smoothly at first for my heavily configured component as well, but then it suddenly lost its connection to the main.

Are these components coming from a published library? When an update doesn't propagate, are you editing in the library file itself or in a file that uses it?

I haven’t published these components yet. I’m working in the same file where they were created and I’m inserting them as instances within that same file.

On an instance that doesn't update, click into it and check the right sidebar—is the whole slot showing as overridden, or just specific container properties?

For the case I’m exploring, it seems that the entire table component, including its slots, is marked as modified. In addition, the nested row instances that also contain slots are marked as modified as well.

--

I’d like to understand whether this is an inherent limitation of Slots or whether you agree that this is something that should be addressed.

From my perspective, this is clearly a bug. If we can’t support multi-level nested slots or basic component–instance relationships, it significantly undermines the value of using Slots in the first place.

If this behavior is expected, I’d appreciate a clearer understanding of the current limitations and your roadmap for improving Slots. I’m currently building a design system around them, and based on both my own experience and feedback from others in the community, relying on Slots in their current state appears to be a risky decision.

Could you share any plans or estimated timeframe for addressing these limitations and investing more in the Slots as a feature?

Thank you.

Hey, ​@Iasonas Georgiadis 👋 Thanks for the examples. I located your support ticket (ID 1939370) and see our team is taking a look. Please let me know if I can help you in any other way — Jaycee

The same issue. Child components with slots aren't updated when the parent component changes. It would be great if I could be notified as soon as this bug is fixed.

Hy Jaycee, this ticket is unrelated to the slots one, it was about a swapping instance issue on another level.

Hey, ​@Iasonas Georgiadis 👋 Thank you for (gently) letting me know I was mistaken in this case. I appreciate you. If this needs a separate support ticket, we can do that together. Since you already provided two videos and many details, I’ll get it opened and link the case number back here for you. Talk soon! — Jaycee

Thank you ​@Jaycee Lewis, I have already opened a ticket for this matter.