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
  • 3171 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
    SantiQ
    SantiQ
    New Member
    March 6, 2026

    Same problem! Bumping this

      Michael_Dulin
      Michael_Dulin
      New Member
      March 6, 2026

      So happy to see I’m not the only one.  Even when I roll back to the previously published versions of my library, the error is still there.  It has completely blocked my team’s work today

       

        Hyun Kim
        Hyun Kim
        New Member
        March 6, 2026

        I can’t for the life of me figure out why I’m getting this error message on an instance of a component that works locally in the library file but when I pull it in as in instance in a file linking it I get the error. "The properties and values of this variant are conflicting." I haven’t changed the properties since I just instantiated it and I have no ability to change them because of the error. I went and checked the component and redid the properties several times and published and updated the library change from the design file. 

         

         

        I dont know if this is a clue but I changed the properties to all booleans from a single property with 3 different values and a single boolean. Could it be there’s a ghost property that’s causing the conflict? 

        How do I resolve this issue?

          anna everhart
          anna everhart
          New Participant
          March 6, 2026

          THIS IS DRIVING ME INSANE!!! Happening to mine too I can not figure out why; they were not broken before slots updates and i havent made changes and now they are broken

          anna everhart
          anna everhart
          New Participant
          March 6, 2026

          Same issue for me!!! its driving me nuts nothing changed and now all of a sudden this is happening  (the only thing that changed was slots) 

           

            Twok
            Twok
            New Member
            March 6, 2026

            Having this same issue today. Glad im not the only one

             

              Brandon Desormeaux
              Brandon Desormeaux
              New Member
              March 6, 2026

              For my design library of components, any time I add a new variant the root component is breaking in all instances. I can use the component in my Library file and it functions. When I take that component and its variants and duplicate them exactly as-is as a new component, it will work. This unfortunately means that any time I make an update (such as adding a filled version of an icon), everything breaks and I need to create a duplicate one from the original in order for me to make this work.

              This certainly seems like a bug as in the Main Component we are seeing no errors. We are able to copy and paste the exact main component and use that without issue. There is something likely out of sync here between the instance and the main component, and this certainly seems like a software bug.

              The attached images show the duplicate components in the file. They are 100% identical as the Menu Item 2 was simply a copy and paste of Menu Item. In the file we can see the error showing when it’s set to Menu Item, and no error when set to Menu Item 2. This issue just arose today for me.

               

                Mauricio Rivera
                Mauricio Rivera
                New Member
                March 6, 2026

                Reporting same issue. Working fine in the morning. Suddenly started having this same issue.

                  Michael_Dulin
                  Michael_Dulin
                  New Member
                  March 6, 2026

                  After looking at this error some more, it seems like the error is happening to any text string or component swap property.  Unfortunately, almost every component in our library has those.

                  Michael_Dulin
                  Michael_Dulin
                  New Member
                  March 6, 2026

                  This bug has stopped our Figma work for the day.

                  Show more replies
                  Terms & ConditionsAccessibility statement