Yup, exact same issue happening to me as well today. I am using Figma Sites and a design library in Figma Design and my entire Site is messed up now. Only the default variant is showing on everything instead of my selected variant so everything is broken… Please fix this Figma!

Noting that making a small change and republishing isn’t fixing it for me, and building a simple component from scratch still produces the same error. All errors seen are for instances in outside files, not the authoring file.

I got slots update today but this doesn’t feel like an even trade...

Yeah setting as solved doesn’t seem like a great process

This is happening to me as well, even though I don’t have the slots update. I even tried creating/publishing completely new components and the properties still say they’re duplicated. Seems like the “Variant” property in particular has issues, since the “Instance Swap”, “Text”, and “Boolean” properties are still configurable outside my Library file.

Why is this solved? It’s most definitely not.

I am seeing the same issue, even with components that I have not edited recently. 

I cant use variants from the DS library. This issue still persists. Why is this tagged as SOLVED?

same problem here.. :( 

The issue is resolved for me now, thanks to the team.

Bug Report: Native Slots Beta Conflict with Legacy Instance-Swap Pattern

Category: Components / Slots (Open Beta)

Summary

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."

Environment

• Figma Slots (Open Beta, rolled out March 5, 2026)
• Components using native slot properties with nested component instances inside the slots

What Happened

Components using the new native slot feature began failing after the beta rollout. All content inside affected slots was cleared and the variant conflict error appeared, despite no changes being made to the parent component or its slot structure.

The error also blocked resetting the instance to default, making it impossible to recover without diagnosing the root cause.

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.

Why It's Hard to Diagnose

• The error surfaces on the parent component, not on the nested component containing the instance-swap
• Only one nested instance was the cause, but all slot content across the component failed
• The variant conflict error message points toward the parent's variant/property structure, misleading the investigation away from nested components
• There is no clear indication in the UI which nested component is the source of the conflict

Resolution

Removing the instance-swap property from the nested component used inside the slot resolved the error and restored normal slot behavior.

Suggested Improvements

1. When a slot conflict is caused by a nested component, surface the error on or near that nested component rather than (or in addition to) the parent
2. Add a warning when a component containing an instance-swap property is placed inside a native slot, if this combination is currently unsupported
3. Document this conflict pattern in the Slots beta documentation
4. Investigate restoring compatibility between instance-swap properties and native slots. Instance-swap and native slots serve complementary purposes — instance-swap enforces consistency by limiting designers to approved options, while slots allow open flexibility. Both are valuable, and having them work together is important for design systems that need to balance flexibility with standards. Since this combination worked before the most recent release, full compatibility should be achievable.

[This posted was merged by a moderator from Native Slots breaking when nested component uses Instance-Swap property to "Properties and values of this variant are conflicting" - but they are not on 07-Mar-2026.]