Hi,Over de last few weeks our team is experiencing more and more inconvenient and work impeding bugs in Figma. Over the last few days we’ve been struggling to find workarounds for instances for which the ‘Variants could not be loaded’. It’s really awkward and unreliable if we design something and random things cause the designs to change. To name some that really affect our collaboration with other teams:Instances of components sometimes appear empty (this seems to be related to slots?). Changing properties for components with slots no longer work if the content within the slots was edited. Placement of layers seems ‘off’, until the layer is selected and automatically restores its placement. Instances of components that are inserted (Shift + i) are completely empty and void of layers. Copying main components from our spec files to our UI kit causes the variants to become duplicated within resulting in twice the number of variants and causing conflicts. (I’ve raised a support ticket for this.) Opening or reloading a design file causes some layers to change from filling the height to hugging the height or vise versa. (This, again, can most often be fixed by selecting the layer.) Inability to edit text layers until I reload a design file. Crashes of plugins when used with layers in slots, most notably Contrast.I assume that a lot of work is being done for the upcoming Config, but I’ve lost so much time over the last 2 days in trying to deal with these issues. I would really appreciate if Figma can prioritize fixing their bugs before introducing new features.

New Member

Question

Increasing amount of bugs

Forum|Forum|3 months ago
May 29, 2026
24 replies
427 views

Hi,

Over de last few weeks our team is experiencing more and more inconvenient and work impeding bugs in Figma. Over the last few days we’ve been struggling to find workarounds for instances for which the ‘Variants could not be loaded’. It’s really awkward and unreliable if we design something and random things cause the designs to change. To name some that really affect our collaboration with other teams:

Instances of components sometimes appear empty (this seems to be related to slots?).
Changing properties for components with slots no longer work if the content within the slots was edited.
Placement of layers seems ‘off’, until the layer is selected and automatically restores its placement.
Instances of components that are inserted (Shift + i) are completely empty and void of layers.
Copying main components from our spec files to our UI kit causes the variants to become duplicated within resulting in twice the number of variants and causing conflicts. (I’ve raised a support ticket for this.)
Opening or reloading a design file causes some layers to change from filling the height to hugging the height or vise versa. (This, again, can most often be fixed by selecting the layer.)
Inability to edit text layers until I reload a design file.
Crashes of plugins when used with layers in slots, most notably Contrast.

I assume that a lot of work is being done for the upcoming Config, but I’ve lost so much time over the last 2 days in trying to deal with these issues. I would really appreciate if Figma can prioritize fixing their bugs before introducing new features.

Show previous replies

adamsmasher

Figmate

Hi, @Julia57. That’s unfortunate that you’re also seeing some empty frames with missing layers.

Are these instances of components? If so, can you try the following: Make a “silent” change to one or all components in the variant set, then publish and accept the update? By “silent” change, I mean a very minor change like adding or editing a description, which you then publish and accept. This approach was successful with other cases of this happening, so it should resolve it for you as well. Let me know if you still have trouble!

Julia57

Active Member

@adamsmasher Unfortunately it doesnt work for local components,since a file can’t really accept upates from itself, I think 😅 I’ll definitely try it with the non-local components though

adamsmasher

Figmate

Oh, some are local to the file, @Julia57? Yea, that approach wouldn’t work… 😅

Are you seeing it with instances of the components or the original component itself? If it’s an instance, maybe the same kind of solution would still work - make a tiny change to the originating component in the file and see if that updates the instance. Either way, let me know if you still have trouble!

Julia57

Active Member

@adamsmasher I mean I can force it to fix itself by clicking on it, or making a change like you suggested, but later on it just breaks again, because it’s not a structural bug, but a visual rendering bug.

adamsmasher

Figmate

Ok, thanks for confirming. Would you be able to share the file with support-share@ figma.com with view access (this won’t affect your billing)? I’d like to create a ticket for you with our Technical Quality team so they can take a look.

Julia57

Active Member

@adamsmasher Sure, thanks a bunch.

https://www.figma.com/design/6F3i5W1e6Wa5R0MaIW7gad/%F0%9F%8E%A8-Beratung-%E2%80%93-Design?node-id=1323-47823&t=AraEt0mjxP48NEza-11

I’ve linked you to this particular component, which bugs out pretty consistently. You can see that one of the instances appears off-center, and it springs back when clicked.

EwaKaminska

New Member

Thanks for your reply, @EwaKaminska - that’s unfortunate that this is creating this much extra work for you and your team. Just to make sure I understand you correctly when it comes to your new pattern with slots, you’re saying that when you change the parent component to a different variant that the content in the slot is lost? That is not expected behavior if that’s what you are seeing - once you change the content of a slot, that edited content is no longer linked to the parent and should be unaffected by variant swaps.

However, component properties are no longer supported on layers inside a slot. It sounds like you may be doing that, but correct me if I am wrong. Hmm… From what I understand of your component setup with a Slot wrapper, it may help to keep component property bindings outside the slot wrapper boundary. By binding variables at the parent level to variants, etc, you can achieve the intended effect by changing modes rather than directly variant swapping (see our help article on binding variables to variant instances - or this video if you prefer that format).

Let me know if I haven’t understood your setup or the issue correctly, or if you do try what I suggested and continue to have trouble.

thanks @Julia57 for your reply. We can’t bind variables of the content inside a slot to a parent component like ds-card, this would be pointless to have a design agnostic component like card with a slot. This is what slots should be.
We have a second component setup, where instead of Figma Slot, we have a autolayout wrapper with a placeholder component inside and we replace it in an insance of ds-card inside a new specific component. And the issue is exactly the same.
The problem is that structure of components is the same on the parent component, and changes in that parent reset properties of its children. This is definitely not expected behaviour. Especcialy that it worked for years correctly, but it become a problem lately.

Julia57

Active Member

@EwaKaminska I don’t have any issues related to bound variables. I do think that the card itself should be design agnostic, but that wrapping the configured card into a new master component should be a valid way to define content. Unfortunately it doesn’t work that way. My issue is also not related to variants or properties. It’s that I am seeing a purely visual rendering bug related to the layout.

adamsmasher

Figmate

Thanks for sharing that, @Julia57! I made a ticket for you with our Technical Quality team and included the file with it. You should hear back shortly via email - thank you for your patience!

Julia57

Active Member

@adamsmasher thank you!

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO