Hey Ben, I’ve just created a support ticket on your behalf. Your ticket number is #879092, for reference. Could you please send the URL of the file to the team, and add support-share@figma.com as an editor on this file so they can take a closer look?

Also, please confirm the exact steps you are taking to produce the error? Or if possible can you send a recording showing this?

Hi, I’m getting the same error, I recorded a video.

After an error, one of the options crashes from the component. There was no error before adding the new option.

We have gotten this error in our component library file a few times. It creates a huge challenge because we can no longer edit global components that we use in all of our design files. I also managed to capture a video of this happening when trying to add a variant property. It would be really nice to know why this happens and if there is a way to stop it from happening in the future.

I keep getting this and it’s making me crazy, there are no dependency issue in my component, that component was working fine for MONTHS and it broke all of a sudden
I spent an hour trying to fix this issue but nothing works, I’m getting desperate

Edit : Ok found what the issue was, I feel like Figma shouldn’t autofix this as it creates more confusion and frustation than anything. It should just point to the conflict. Fixing it made me lose time, and lost all of my logic for that one variant.

Also please note that this didnt happen the moment I added the new nested component, making it much more confusing : it was just not working (I could see my variant, but not the nested one inside of the variant)

If everyone has that message, I was reusing the component I was working in from another nested component, so making them dependent