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
    Tom Reem
    Figmate
    Tom Reem
    Figmate
    March 8, 2026

    Hi ​@Becca_Fuller, thanks for flagging this, and sorry you’re running into the issue as well.

    I’ve moved your post into this new thread so we can track related reports in one place while we continue monitoring what’s going on.

    Paulo_Custodio1
    Paulo_Custodio1
    New Member
    March 8, 2026

    Why is this marked as solved. Its clearly still NOT RESOLVED.

      John_L
      Figmate
      John_L
      Figmate
      March 8, 2026

      [Possible solution for files that are not on a branch and do not contain branches]

      Hi ​@Shawn0000001 and ​@Paulo_Custodio1,

      Following up on Tom’s note, sorry about these issues you are experiencing. We’ve identified another solution for files that are not on a branch and do not contain branches.

      If you are on a file that is not a branch and does not contain branches, can you try the following on the instances that are showing the error?

      1. Reload the file with the error.
      2. Select an instance that is erroring.
      3. Run the “Repair component connections” quick action. (Command K on MacOS or Control K on Windows, then type in “Repair component connections”, then select and press enter).

      Can you let us know if this workaround helps?

      Thanks,
      John

        Celyn_L
        Figmate
        Celyn_L
        Figmate
        March 9, 2026

        Hey everyone — thanks so much for flagging this and for bringing it to our attention.

        I understand that slots are not carrying over to other files, and we’re investigating this further with our Engineering team.

        I’ll update this thread as soon as I hear back.

        Thanks so much for your patience in the meantime.

          Marco K
          Marco K
          New Member
          March 9, 2026

          Re: 

          [Possible solution for files that are not on a branch and do not contain branches]

          Hi ​@Shawn0000001 and ​@Paulo_Custodio1,

          Following up on Tom’s note, sorry about these issues you are experiencing. We’ve identified another solution for files that are not on a branch and do not contain branches.

          If you are on a file that is not a branch and does not contain branches, can you try the following on the instances that are showing the error?

          1. Reload the file with the error.
          2. Select an instance that is erroring.
          3. Run the “Repair component connections” quick action. (Command K on MacOS or Control K on Windows, then type in “Repair component connections”, then select and press enter).

          Can you let us know if this workaround helps?

          Thanks,
          John

           

          This is working for me, however, I need to run this individually on each component that has this error. In my case, there are many… Is there any way to fix this globally within a Figma file?

           

           

           

            Irina004
            Irina004
            New Member
            March 9, 2026

            +1 bumping. Having the same issue 

              Jeremie Paret
              Jeremie Paret
              New Member
              March 9, 2026

              Still not fixed. “Repair component connections” works but it’s temporary and very time-consuming.
              QA your releases please you’re not a small startup.

                Shawn0000001
                Shawn0000001
                New Member
                March 9, 2026

                [Possible solution for files that are not on a branch and do not contain branches]

                Hi ​@Shawn0000001 and ​@Paulo_Custodio1,

                Following up on Tom’s note, sorry about these issues you are experiencing. We’ve identified another solution for files that are not on a branch and do not contain branches.

                If you are on a file that is not a branch and does not contain branches, can you try the following on the instances that are showing the error?

                1. Reload the file with the error.
                2. Select an instance that is erroring.
                3. Run the “Repair component connections” quick action. (Command K on MacOS or Control K on Windows, then type in “Repair component connections”, then select and press enter).

                Can you let us know if this workaround helps?

                Thanks,
                John

                This works, but I have hundreds of components in a complex file and a tight deadline, and the repair for each is slow to process, so hopefully there’s a forthcoming global fix

                  John_L
                  Figmate
                  John_L
                  Figmate
                  March 9, 2026

                  ​@Jeremie Paret - Thanks for trying out the fix and the additional feedback. Apologies again for the issues here. Can you say more about the temporary nature of the fix? One thing to try might be to reload the design file to make sure you have the most up to date code. We don’t currently expect the fix to be temporary in nature.

                  We are also actively looking into a tool that is lighter weight and can be applied more easily across the file. Thanks!

                   

                  Dan_Millson
                  Dan_Millson
                  New Participant
                  March 9, 2026

                  We don’t currently expect the fix to be temporary in nature

                  We are also actively looking into a tool that is lighter weight and can be applied more easily

                   

                  Thanks to the team for getting a functional fix up. I’m glad I stopped making things worse for myself this week by deciding to stop working in Figma after the issue was reported on Friday. For a while, I thought it was just an issue I caused myself.

                  Thankfully I had other busy work that I could do while the SaaS was broken.

                  Maybe if you are pushing such changes to the core of component relations and introduce bugs like this (just hypothetically, in future), it could be good to have a functionality to trigger a callout to warn users that they are making potentially problematic downstream changes due to a known issue. I know I’ve seen a scary banner about “updating figma or lose access” or “downtime notice” before.

                  I hope that you get the tool for fixing large documents available for those affected.

                  Can you share anything about what caused this issue under-the-hood?

                  Show more replies
                  Terms & ConditionsAccessibility statement