Skip to main content
Dan Sagher
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 named. But 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

    Show previous replies
    Dan_Millson
    Dan_Millson
    New Participant
    March 10, 2026

    ​@John_L I appreciate the transparency on it. Thankyou.

      Megan Harris
      Megan Harris
      New Member
      April 16, 2026

      FWIW, I was able to fix this on a component by dragging the affected instance outside of the component group (so it was its own component) and then dragging it back into the group. No idea if this will work all the time, but it very quickly fixed what I was trying to figure out for a long time!

      Terms & ConditionsAccessibility statement