Skip to main content
Question

Modifying a slot content disconnects the entire instance from its main component

  • June 15, 2026
  • 3 replies
  • 80 views
Feline_Hu

I’ve got components with slots in it and componetized for design file efficiency. Instances work great at first, updates to the main component cascade as expected. But the moment I edit the content inside a slot on an instance, the entire instance disconnects from the main component. Not just the slot. So any future updates from the main component stop cascading to that instance, and the only fix is a full reset which removes the slot content I just customized. 

Expected behavior 
I would expect that the modifying slot content is treated like any other override (e.g. text or swap overrides). It should not disconnect the entire instance from the main component updates.

Is this a known limitation? I would love to hear if there is a workaround or if this is planned for improvement!
 

 

    3 replies

    Fabrice Brzycki

    Same here! Our entire design system is built around slots and depends on them, so this issue currently makes it completely unusable for us.

      John Kim
      • John Kim
      • New Member
      • June 22, 2026

      I have the same issue! 

      Kerry_Johnson

      Apparently this is working as designed as per the quote below.  To me it makes absolutely no sense why components in the slot become immediately unlinked with the slightest change.  This runs into the same issue as detached components, but this time it comes with a reset button.

      I can maybe understand if there was a substantial change to the component in the slot, but… even changing just one character of a text layer, Figma slot throw its hands up like you just summoned some Matrix level paradigm shift and disowns the link.

      With this change I’m thinking their node system must be really cursed or their team out of touch with how users want to use slots, and if speed was the issue as I’ve read in some other product decisions… I’m sure we are fine with waiting for things to sync up accurately versus leaving things out to try at the slightest bump.

      And maybe our worries will be clear in time; communication goes a long way especially as guinea pigs to the feature.  Here’s to hoping they work towards a more sensible solution than just abandoning the link, because that basically kills half of slots usefulness for most of us (the other being able to add more items and reposition freely).

       

      [...] as of April 7th, there was a behavior update to slots. Edited slot content no longer links back to the main component, which means library updates won't automatically propagate to slot content that has been modified. This was an intentional change for experience consistency. If your slot content has been customized at all, it would explain why variable assignments from the library aren't coming through.

       

      Terms & ConditionsAccessibility statement