Skip to main content
Question

Nested instances reset to default when applying parent modifications like booleans

  • January 5, 2024
  • 14 replies
  • 1294 views

Sasch

Hi, I’m facing a strange behaviour right now and I did not find a way to make it work yet…Maybe you folks can help me find a solution or point me in the right direction.

My plan is to create a sidebar navigation pattern where designers can modify the menu structure easily.

The structure of the example includes a “Single Item” component set where all the different navigation link type are collected (e.g. Headline, Link, Subline, Divider, etc.) and a “Section” component set that is used to allow the designers to choose how many navigation items they want to have in a section.

Now to the strange behaviour. When I use the “Mobile” boolean on the “Single Item” component all works as expected. Inactive “Mobile” is full width and active “Mobile” is max-width of 68px. See an example below:

Now when I apply the same settings to a “Section” component only the unchanged link types have the custom text I applied earlier. All link items that have been modified are overwritten by their default state. What I would expect is the “Headline” and “Subline” to have the modified text like in version where mobile is not active. See an example below:

It’s strange to me that, for example, the nested instance is still remembering that I changed it to a “Headline” type but not remembering the text I entered. This way its impossible to allow the designers to easily change the sidebar to collapsed without changing the content for the mobile version manually. What am I missing here?

Here is a sample file to see the behaviour in action:
custom_override_bug.fig (84.6 KB)

14 replies

Gayani_S
Figmate
  • Community Support
  • January 15, 2024

Hey Sascha, I’ve checked internally and got the confirmation that this is not an expected behaviour. Please reach out to our support team, they can investigate further and file a bug report on your behalf.


DeniseN
  • New Member
  • May 10, 2024

My team and I are also experiencing this issue, was a solution ever found?


Sasch
  • Author
  • May 13, 2024

Nope but I was too busy to reach out to the support team…we still have this issue.


Gayani_S
Figmate
  • Community Support
  • May 16, 2024

Hey @Sasch, sorry to hear that you’re still experiencing the issue.
I’ve just created a support ticket on your behalf. Your ticket number is #1002446, for reference.
Our support team usually takes up to 24 hours to reply back to emails - tends to be quicker than that in normal circumstances. However, please be aware that we are facing increased contact volume so there might be a delay

Appreciate your patience in the meantime!


Gayani_S
Figmate
  • Community Support
  • May 16, 2024

Hey @DeniseN, I am happy to have an eye on the ticket from the user when it’s being processed by our Support team to give you more information about it.

Alternatively you can reach out to the support team directly via this form: ​https://help.figma.com/hc/en-us/requests/new?ticket_form_id=360001731233.
Please also share your file link with our team and invite support-share@figma.com directly as an editor (this won’t affect your billing at all).

Thanks!


Sasch
  • Author
  • May 17, 2024

Hi @Gayani_S thank you for creating the support ticket 👍 I will let you know in here if it was a bug, if yes how we fixed it or if I was just using a wrong approach.


Gayani_S
Figmate
  • Community Support
  • June 10, 2024

Hey @DeniseN, wanted to give you a current update on the ticket.

Our engineering team have been investigating this issue and to be transparent this will not have an immediate resolution as they need more time to investigate this and fix it due to its complexity within our override logic.

We can’t promise a quick fix, and please know that our engineering team is aware of the issue and will work towards finding a solution in the future.

Please let me know if you have any further questions.


JustJest
  • New Member
  • June 19, 2024

I am also experiencing this issue. @Gayani_S I know you said that you cannot promise a quick fix but is this bug currently in the queue to be investigated and worked on. There seem to be a fair number of issues related to this on the forums. Just a few I have found.

Also, where is the Fix Instance Overrides command that this thread is talking about?


Gayani_S
Figmate
  • Community Support
  • June 20, 2024

Hey @JustJest, thank you for reaching out and also collecting these issues!

I’ve went through these post and I am seeing slightly differences in the issues. Could you explain what you’ve been experiencing? It would be best to have a screen recording, so I have a better understanding.

Thanks in advance!


Ivan_Perez

I don’t know if this error is related but what happens to me is that i have nested instances inside other components and whenever i update some property on an instance it resets every property of the component, I don’t know if I have designed wrong the component and I don’t know how to solve it, it’s driving me crazy. 😩


Francisco_Caballero

To prevent issues with the Prototype and Components with different variants (states like collaped=true/false for instance), each layer must have its name since it will be used as class names during the transitions.

Keep a clean naming convention, and be sure that nesting is properly defined.


Cisil Calipinar

Hi everyone, I’m running into a serious issue with modals in my Figma file and I’m hoping for some guidance.

I worked on several modals in a branch. Everything was correct there, but after merging the branch back into the main file, many of the modals lost their text content and seemed to reset to a default state.

What’s confusing is that some modals in the same flow that I did not modify also reset themselves, while others remained unchanged. So the situation is inconsistent:

  • Some modals I edited lost their text and reverted.

  • Some modals I never touched also reverted.

  • Some modals stayed completely fine.

This happened right after merging, so I’m unsure if this is related to components, variants, or something with branching behavior. I’ve checked for overrides, but the resets seem unexpected and inconsistent.

Has anyone experienced something similar or knows what may cause this? Any suggestions or troubleshooting steps would be greatly appreciated.

Thanks in advance!

PS: this kind of behaviour happened with some CTA components too. But in that case, all the text variables of the CTA was detached and i needed to fix them manually
 


 

 


josh.paris
  • New Member
  • November 5, 2025

Hi Cisil, our team also just recently had this issue. We ended up having to double click into the component and it fixed itself. We tried multiple times and it kept resetting our merged components. Very weird behavior that I think is a bug.


Novia_LINDSAY

Hi Cisil, our team also just recently had this issue. We ended up having to double click into the component and it fixed itself. We tried multiple times and it kept resetting our merged components. Very weird behavior that I think is a bug.

I experienced this issue today. Following a merge, all of the labels, values, and icons in my components reset to their defaults.