Skip to main content
Lorenzo Brandimarte
Lorenzo Brandimarte
New Member
May 28, 2025
Solved

Buttons components are not linked properly

  • May 28, 2025
  • 3 replies
  • 366 views

Hi everyone,

I really need some help with a file.

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

 

This topic has been closed for replies.
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!

3 replies

Celine_
Figmate
Celine_
Community Support
May 28, 2025

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:

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

  2. 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:

  1. Open the file with the affected instance and select that instance.
  2. Click the main dropdown menu (the Figma logo) in the top-left corner to access the “Actions...” search bar.

     

  3. Search for "Repair component connections”

 

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

Thank you!

Lorenzo Brandimarte
Lorenzo BrandimarteAuthor
New Member
May 29, 2025

Hello,

Thank you so much for your reply.

I found out that the issue was caused by moving the “buttons” components, from the components page to another page.

Because of that, the buttons are no longer linked to their original components.

Manually updating them would be a huge task, there are tons of buttons. Unfortunately, the “Repair connections” function doesn’t seem to help either.

I’ll go ahead and submit a bug report.

In the meantime, if you happen to know a way to fix this, it would be amazing.

P.S. I already tried moving the buttons back to the Components page, but they still don’t work.

Thanks in advance
Lorenzo

 

Celine_
Figmate
Celine_Answer
Community Support
May 30, 2025

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!

    Terms & ConditionsAccessibility statement