Skip to main content
Dan Sagher
New Member
March 6, 2026
Solved

"Properties and values of this variant are conflicting" - but they are not

  • March 6, 2026
  • 102 replies
  • 3172 views

I have a design system that I published as a library. I’m consuming this library in another file for a slide show. Up until now, I never got an error when trying to access variants in the slide show file. But as of today, I am getting this message for a seemingly random assortment of instances:
 

“The properties and values of this variant are conflicting. Change the applied values on this variant to resolve this.”

 

I don’t get this error when interacting with variants inside the authoring file. 

 

I looked up this error message on the Figma forum, and it says it appears when Figma detects that two variants are identical, regardless of whatever they’re namedBut in my case, the variants are absolutely not identical. They have many differences in names and values and they have never produced this error either on the authoring or the consuming side until now. 

 

I saw that Figma dropped the “Slot” property recently (love it). I’m wondering if this update could have led to this error?

Best answer by John_L

Updated guidance for those following this thread:

  • If your file is not on a branch and does not contain branches:
    • Reload the file.
    • Select the instance showing the error (or select multiple instances or the entire page if there are many different instances showing the error).
    • Run the “Repair backing component set” quick action (Command K on MacOS or Control K on Windows, then type in “Repair backing component set”, then select and press enter).
    • This should clear the error. If you notice that the ordering of values in the dropdown menu for each property are different than the source, you can further run “Repair component connections” to resync with the backing component set.
  • Otherwise:
    • Make a small change to the backing component set of the instance that has the error. Re-publish the component set and accept updates in the consuming file(s) that have the error.

       

102 replies

Mike Nizinski
New Member
March 6, 2026

Same bug. I assumed it had to do with the rollout of slots. 

Ariana_Moros
New Member
March 6, 2026

same issue!

Heather Edwards
New Member
March 6, 2026

and while i was able to walk it back, any new changes are getting all jacked up. Even tried recreating. 

Heather Edwards
New Member
March 6, 2026

basically any new componant I am making in my library is breaking

Nathan_Dana
New Member
March 6, 2026

Same, please fix ASAP

Federico Stampini
New Member
March 6, 2026

i also thought i messed up something but now i’m sure it’s a bug that is blocking my release for today. 
please fix it ASAP🙏

ksn
Figmate
Community Support
March 6, 2026

Hey everyone - I apologize for the trouble.

This is a bug our engineering team is investigating as a high priority right now. I will be merging existing topics to this one, and will continue to add updates as I receive them

Thank you for your patience.

Alexey
New Participant
March 6, 2026

Same here

Hari J
New Member
March 6, 2026

Hey everyone - I apologize for the trouble.

This is a bug our engineering team is investigating as a high priority right now. I will be merging existing topics to this one, and will continue to add updates as I receive them

Thank you for your patience,

Thanks for acknowledging this bug, is there a timeline as to when a fix will be available?

ksn
Figmate
Community Support
March 6, 2026

@Hari J At this time, I don’t 😔 but I’m active in the conversations about this, and I’ll get updates here as soon as I can.

 

EDIT: While this continues to be worked on, you can continue to keep tabs on this topic, and also on our status page as well.

 

Appreciate your patience, everyone.