After duplicating a project, some of the components stopped working properly.
The “Go to main component” option doesn’t appear at all when I click on a button.
The only thing I can do is click “Restore component,” which just creates a duplicate of the component in the relative page (very weird to explain).
Oddly, this only affects the buttons, other components seem to be working fine.
Any quick advice or solution to fix this?
Thanks in advance, Lorenzo
Best answer by Celine_
Hi again Lorenzo, thanks for the update! I can see in the backend that recreating the file did the trick—glad that worked for you!
For anyone else experiencing a similar issue, here’s another workaround that might help: Next time this happens, you may also want to try making a small, non-operative change to your main component and publishing it once more. This change could be something very small like editing the component's description. Then once you've done this, accept the library update when prompted from your working file.
This will force your components to re-render and hopefully repair any broken instance connections.
I’ve gone ahead to mark as solved the topic here. Thank you!
Hey Lorenzo! It’s possible that the link to the main component broke when you duplicate it, especially if the original file was part of a library.
As a temporary solution, here is a couple of things you can try:
If “Go to main component” is missing and you only see “Restore component,” it usually means the instance has lost its source link and is now a detached local version. In this case, you might need to relink it manually from the original library. For example, you can ‘swap the instance’ when selecting the broken component, then choose the correct version from the original library.
Try using “Repair component connections” command in Quick Action. This command has a similar affect to fetching the most updated version of the main component, without you having to manually change and re-publish the main component and accept updates in subscribed files.
Please follow these steps:
Open the file with the affected instance and select that instance.
Click the main dropdown menu (the Figma logo) in the top-left corner to access the “Actions...” search bar.
Search for "Repair component connections”
Run this command
If that still doesn’t help, feel free to submit a bug report here, our support team can investigate it further. In the form, please also share your file link and give can edit access to the affected file with support-share@figma.com (this won't affect your billing at all) so the support team can take a look at it.
Hi again Lorenzo, thanks for the update! I can see in the backend that recreating the file did the trick—glad that worked for you!
For anyone else experiencing a similar issue, here’s another workaround that might help: Next time this happens, you may also want to try making a small, non-operative change to your main component and publishing it once more. This change could be something very small like editing the component's description. Then once you've done this, accept the library update when prompted from your working file.
This will force your components to re-render and hopefully repair any broken instance connections.
I’ve gone ahead to mark as solved the topic here. Thank you!
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
