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

cyannide
New Member
March 6, 2026

When on a master component,  Slot won’t show up as a property in the + properties section on the right panel (I only see from Variant to Instance swap options) and neither when right clicking inside the nested frame in that component.

I have already tried to reload/restart figma multiple times

Inesa Shevchenko
New Member
March 6, 2026

Same issue! 

Caro52
New Member
March 6, 2026

Currently experiencing the same bug!

JScarani
New Member
March 6, 2026

Having this issue too. I just added a new variant to a table component and it’s throwing this error now even though there are no conflict. It works perfectly fine inside the design system file where it’s located but throws the error when used in any other file.

Caro52
New Member
March 6, 2026

Same bug, I kept trying to rebuild my component thinking I was crazy!

Nathan_Dana
New Member
March 6, 2026

Also experiencing this issue.

Heather Edwards
New Member
March 6, 2026

Wait help I am having this exact same issue. 

Ariana_Moros
New Member
March 6, 2026

Same issue, this is realy messing up my work dayyy

Ariana_Moros
New Member
March 6, 2026

same issue. tried unpublishing the library and republishing it, tried a test variant and named everything 1,2,3 nothing has worked

halcyon100
New Member
March 6, 2026

We’re having the same issue. All of our design system files are throwing this error, while showing no issues (or changes) in the core UI kit.

Figma - we need to know when this will change - this is breaking to our design system.