An error occurred while adding an instance of this component

Seems like you found a bug, you should send a report to Figma Support via the support request form or support@figma.com.

Thanks, Gleb. I’ve just sent the report to the Figma Support 👍

Hm… unfortunately the first option to Unpublish the library only resulted in an error about unpublishing the library haha. The second one is harder to pinpoint, as it doesn’t really indicate what component is the bottleneck.

This happens to me often in our icons file. I’ve done both of these solutions multiple times already. I always do (2) first but when that doesn’t work, I end up doing (1). Sometimes on rare occasions, that doesn’t work either so I just end up doing (2) again which usually fixes it. Basically, just going back and forth of doing the two options which is a bummer and a huge time suck.

Hopefully, this gets fixed soon.

Hey, I’ve also been getting this issue with our icon library. In order to fix it I’ve been modifying the variant slightly (like updating the description of it) and republishing. It works, but definitely is an insane time suck.

Hmm, sadly have been getting this error now too. Unpublish and Republishing Library did not work. But making changes to a component did.

Makes the Asset panel workflow kind of useless since it’s just giving errors if you try to drag an item from the Designsystem for example. Hoping for a fix soon.

Hello,

Two days I go a colleague got an error message when trying to add a component from our common library. For me, it still works without issues (On macOS)

We have already tried these two suggestions I found on a similar thread, but they didn’t work.

(1) Republish
Try to unpublish and republish the library that has an error. Unpublishing a library won’t break any existing connections with subscribed files.

(2) Update the component which has an error
Try to make changes to the main component (such as changing the opacity to something like 99%). Publish the update of the component to the library. Accept the update in the other files using that component.

This is happening for both the Web and the desktop app on windows.
Any suggestions?

Thanks a lot.

Closing and re-openning desktop app has helped me.

+1, Closing and re-opening the desktop app worked for me too

I closed the file tabs within Figma before quitting and re-opening the desktop app, and that worked. Simply quitting Figma while the tabs were still open and then re-opening didn’t work for me.

Hello guys,

I’m facing a similar problem here. I have tried all the solution that you guys mentioned and it didn’t work. After doing analysis and troubleshooting here and there, finally, I can solve it after checking the broken main component and pushed override the instance contained by the broken component.

This is happening for me as well. Neither of the solutions worked for me. I was trying to utilize the Material Icons library file published by Google. I’m wondering if it’s possible that the file is just too large with that many components and variants all trying to be loaded at once. I’ve decided to stop using the file for now since it’s not working.

My work machine is on a pretty locked-down network. On a hunch I tried this same operation on my personal machine and the very same files worked fine. So, I just wanted to update here that network issues may be the cause here for some. This is fixed for me for now, working on my personal machine. Long term though I would love some help from Figma so I can do work on my work machine. 🙂

Just had the same issue. After unpublishing and republishing the library I got an error about a text style that would not publish. I removed it and that fixed the issue. So potentially there is a single component/text style causing the whole library to error, you just need to work out which one it is…

Thank you! After trying the other solutions with no success, this solution solved the problem.

We had this problem four days ago with a large number of our components. We tried closing the tabs and Figma but this didn’t work. I had updated a component that morning so I published changes and while this didn’t work immediately, the problem went away some 15-30 minutes later. Hard to say it resolved as a result of the updated component (not sure if this specific component was a problem one to start with), or if generally republishing the library helped, or if it simply fixed itself.