Skip to main content
nicholaskaschak
New Participant
September 1, 2026
Question

Double nested instance resets when changing main component variant

  • September 1, 2026
  • 3 replies
  • 46 views

I have a button component that I had built a long long time ago before Figma changed how variants worked / a lot of the new functionality was built that made them more flexible.

This component is set up where I have a skeleton for a button with two sizes and a bunch of possible toggles (for icons, labels, etc), a second component which includes that skeleton as an instance which has all of the state / color variants, and a third icon-only component with specific dimensions for each size to keep them square that has the main button component with the skeleton instance nested within it.

My issue is when using the icon-only button and changing the variant of the underlying button component (e.g. to change the style), and then changing the size of the icon button, the skeleton instance resets, undoing all overrides to the skeleton. This only happens when changing to a different variant of the button component - if I use the default button variant and make changes everything works fine.

I’ve included a screenshot showing the layer structure that shows that the skeleton component is resetting - you can see how the “test” name of the skeleton instance resets to “Button Skeleton” in this scenario. This used to work fine but somewhere along the line something happened thats causing this to no longer work correctly. Ideally I’d rebuild this component to not have these nested instances but with them being used all across our app that would be a large undertaking to update.

 

3 replies

Tom Reem
Figmate
Figmate
September 1, 2026

Hey ​@nicholaskaschak — thanks for laying this out, and for including the screenshot of the layers.

Reading through this, I completely understand how this reset is disruptive to your workflow across your app. What you're describing sounds like it’s related to change preservation. Figma does try to carry overrides across a variant switch, but only when specific criteria around matching layer names and properties are met. Worth measuring your skeleton against those.

A few things that would help me take this to the right team:

  • Can you confirm the exact sequence, so I can try to reproduce it? I'm reading it as: Place the Icon Button → change the nested Button's variant → then change the Icon Button's size. Does the reset land on that last step?
  • Do the skeleton, button, and icon button live in the same file, or do any of them come from a published library? If a library's involved, has it received updates recently?
  • When did this stop working? A general timeline will help narrow things down.

If you can share the file with a short screen recording of the reset in action, we can dig into the actual component as well. To do that securely, head to the Support Hub → type “Report a bug” → click Start a chat. Follow the prompts to submit a bug report, and be sure to grant support-share@figma.com can view access. The team will be able to go from there.

nicholaskaschak
New Participant
September 3, 2026

Hey Tom!

Thanks for the quick response!

  1. Yes that is exactly correct
  2. They all exist next to each other in our design system file
  3. I want to say maybe about a year ago? The component was built back in ~2020

I’ll go ahead and create the support ticket! Thank you!

Nick

Jaycee Lewis
Figmate
Figmate
September 3, 2026

Thanks ​@nicholaskaschak 🙌 Let us know if you have any issues getting that support ticket open. — Jaycee