New Member

Solved

"Properties and values of this variant are conflicting" - but they are not

Forum|Forum|6 months ago
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.

Show previous replies

halcyon100

New Member

@ksn Yes, also tried a component update / publish / refresh in file consuming it, with no change. (Also, thank you for your help.)

broom0987

New Member

My workaround is to create a sandbox page on our 'design system' file, change the variants there, and then paste them back into my project file.

ksn

Community Support

Thank you @Jayla_Rediger @halcyon100 -- I took this back to engineering for more investigation.

Steve_Salens

New Member

I’m having the same issue

B

Brandon Grant

New Member

Having the same issue. Spent hours trying to figure it out. I’m somewhat relieved it’s a bug and not something I did.

Sean_Sperte1

New Member

+1 bumping.

Hard to believe even a beta wouldn’t support this functionality; has to be a bug, right?

Danielle Gardner

New Member

having the same issue. changing something like text and changing back didn’t fix it. also using the slots beta.

Michael_Dulin

New Member

@ksn Tried making small changes and republishing. Did not work. Tried rolling back version history and publishing did not work.

Nikolay Ony

New Member

I have exactly the same problem. I republished the library, created a new component, even created a new library with just one component, but nothing helps. The error keeps appearing all the time and the component properties (like variant) are not visible. Slots haven’t been rolled out to my account yet, so I didn’t use them. Everything was working yesterday, but today it suddenly stopped working.

Ryan Harte

New Member

Same here. I’m confused, so is it resolved or not? Also you said ‘May 6, 2026’ which I assume you mean March??

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO