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

martyhosch
New Member
March 6, 2026

Same issue. Tested with a brand new simple AB variant published in a new library. The issue appears there too. 

 

VincentP23
New Member
March 6, 2026

This just happened.

We were using slot beta. The library file has slots in the component, and now when we publishing the library, the slots revert back to normal container in the other files, and shows component error.The file updates resets tons of designs we already laid out!

Having the exact same issue. This has caused some major issues and rework for a large file that was ready for handoff.

March 6, 2026

This exact issue has been happening to me for the past 4 hours. I have my design system where all the components seem to be set up perfectly. Then every single instance of every component says “"Properties and values of this variant are conflicting" and theres absolutely nothing I can fix.

When I copy and instance from the design file into another file where it is published, it breaks, when I paste it back into the design system file, it’s fine again.

ksn
Figmate
Community Support
March 6, 2026

Hey everyone - can you all try making a small change to a component and republishing to see if things have reverted back to normal?

 

UPDATE as of May 6, 2026 @ 3:30 PM PT -- engineering team is continuing to work on the issue. As we approach the weekend, we will do our best to update you. In the meantime, please try the above and comment if you were or were not able to get things to work.

Marking this as the solution (temporarily) to boost visibility.

Mason_Grishin
New Member
March 6, 2026

+1

It looks like if I copy/paste to a new file, the slots is carrying over, but not the existing file with connected library

halcyon100
New Member
March 6, 2026

@ksn I’m still seeing the issue in my file, fwiw. (After restarting desktop).

March 6, 2026

I just restarted everything (even my computer) and it is still happening. I am using the desktop app. 

ksn
Figmate
Community Support
March 6, 2026

Thanks ​@halcyon100 - can you make a small change to a component and republishing it to see if that fixes?

 

cc ​@Jayla_Rediger 

Caro52
New Member
March 6, 2026

@ksn I’m also still experiencing the same issue after restarting desktop app.

March 6, 2026

I just made a small change to a component and republished and it did not work (I appreciate your help very much) 

Meaning the small change did publish, but all the errors still persist