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

Tom Reem

Figmate

Hi @Brian_Saunders — thanks for confirming.

💡 For everyone following this thread: Could you try making a small change to the affected component, then republish it and accept updates to see if things return to normal?

✅ I’m in touch with our engineering team and they identified an issue that was causing the errors reported here. A fix has now been released, and republishing the affected components and accepting updates should clear the errors.

Really appreciate everyone’s patience while we worked through this.

Becca_Fuller

New Member

After the native Slots open beta rollout (March 5, 2026), components built with the new slot properties began throwing a variant conflict error and clearing all slot content — with no obvious cause in the parent component itself.

Error message: "The properties and values of this variant are conflicting. Change the applied values on this variant to resolve this."

What I think is the root cause:

One nested component placed inside a slot was using an instance-swap property. The most recent Slots beta release appears to have introduced a conflict with this combination, causing the entire parent component's slot content to fail.

Importantly, this combination — instance-swap properties on nested components used inside native slots — worked correctly prior to the most recent release. This suggests the conflict is a regression introduced in the latest update, not an inherent incompatibility between the two features.

J

Jayla_Rediger

@Tom Reem Just made a small change to a number of components and republished and everything is back to normal!! Thank you so much!

atlanimator

New Member

Worked for me as well. Thank you!

Darren_Beason1

New Participant

Same issue. I’ve tried everything. Rebuilding a component from scratch, but then found out other designers on other projects were experiencing the same problem. Please fix by Monday!!! I can’t progress on my work without this fix cause it will require me to disconnect everything I work on from my design system.

Tom Reem

Figmate

Appreciate you following up @Jayla_Rediger and @atlanimator! I’m really glad to hear it. 🙏🏻

@Darren_Beason1, sorry to hear you’re still running into trouble with this. To help me share more detail back with our engineering team, could you try the following once more and let me know if it resolves the issue: Confirm that the affected components have been republished, and then accept updates in the consuming files to apply the fix.

If the issue persists after that, please let me know and I’ll pass the details along to the team.

halcyon100

New Member

We’re back to normal, but I have to share, this consumed about 4-6 hours of our time from problem to diagnoses and reconciliation that prevented other work across our team.

Shawn0000001

New Member

Tried the fix and still not working, and since I’m leaning on a slot heavy design system, most components aren’t fully functional and going through each one would cut into time I don’t have.

Darren_Beason1

New Participant

Appreciate you following up @Jayla_Rediger and @atlanimator! I’m really glad to hear it. 🙏🏻

@Darren_Beason1, sorry to hear you’re still running into trouble with this. To help me share more detail back with our engineering team, could you try the following once more and let me know if it resolves the issue: Confirm that the affected components have been republished, and then accept updates in the consuming files to apply the fix.

If the issue persists after that, please let me know and I’ll pass the details along to the team.

Didn’t work.

Darren_Beason1

New Participant

Appreciate you following up @Jayla_Rediger and @atlanimator! I’m really glad to hear it. 🙏🏻

@Darren_Beason1, sorry to hear you’re still running into trouble with this. To help me share more detail back with our engineering team, could you try the following once more and let me know if it resolves the issue: Confirm that the affected components have been republished, and then accept updates in the consuming files to apply the fix.

If the issue persists after that, please let me know and I’ll pass the details along to the team.

Didn’t work.

OK, now I gotta it to work.

Show more replies

What I think is the root cause:

Sign up

Login with SSO

Login to the community

Login with SSO