Instances disconnecting when components are moved from one file to another in same project

Hey @Kendall_Van_Horne, thank you for reaching out!

Is this happening in the desktop app or the browser?

I am not aware of any recent bug regarding component instances disconnecting when copy pasting at this moment. However, could you try opening your file and running a Quick Action called “Repair Component Connections”? 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. I’ve included some instructions on running the command below.

1. Open the affected file
2. From the main dropdown menu in the top left, navigate to the “Quick Actions” search bar.
3. Search for “Regenerate component connections”
4. Run this command

Please let me know if this resolves your issue, happy to help out further.

Glad to know it’s a bug and not an update, but I don’t see this option in the quick actions search…

Hey @Kendall_Van_Horne, apologies for the confusion! I meant “Repair Component Connections”.

Please let me know if this resolved your issue and also can you please confirm if this is happening in the desktop app and in the browser?

Thanks-- this unfortunately does not seem to have resolved the issue. I am still encountering it (using desktop app)

Hey @Kendall_Van_Horne, thanks for updating me on this! I’ve just created a support ticket on your behalf, so our technical quality team can investigate further what’s causing this. Your ticket number is #941211, for reference. Please also share your file link with our team with support-share@figma.com invited directly as an editor (this won’t affect your billing at all).

Our support team usually takes up to 24 hours to reply back to emails - tends to be quicker than that in normal circumstances. However, please be aware that we are facing increased contact volume so there might be a delay.

Thank you,
Gayani

I have the same issue. Nothing happens when I click restore component conection

Hey @Alina_Brender, thank you for reaching out! I’ve seen that the case from Kendall is still ongoing, so I’ve just created a support ticket on your behalf. Your ticket number is #943295, for reference. Please also share your file link with our team with support-share@figma.com invited directly as an editor (this won’t affect your billing at all).

Our support team usually takes up to 24 hours to reply back to emails - tends to be quicker than that in normal circumstances. However, please be aware that we are facing increased contact volume so there might be a delay.

Let me know if you have any further questions.

Thank you,
Gayani

ensure that both the files are sync properly with the cloud storage because sometime issue with syncing can result the disconnect.

Thanls I have shared with u. I have put back all the components now. I need to work on the document. Library filed called data library.

Hey @Alina_Brender, thanks for updating me! I checked your support ticket and did not see any file link, also I did not receive a DM from you. Can you let me know where you’ve shared it with me please ?

I have the same problem when I relocate the master to my design system file.

And when I click instance to go to main component it’s say “Restore component”

Hey @Thanapat_Hongpaisanvivat, thank you for reaching out!

I had a look at the support ticket of the user who flagged this post and there were some interesting findings.

Our support team took the following steps to reproduce the issue:

•   Create new file
  

•   Create new component 
  

•   Create 2 instances of that component
  

•   Cut main component 
  

•   Open new file
  

•   Paste main component 
  

•   Publish library
  

•   Return to original file
  

•   Instances now have "Restore component" in the design panel
  

They’ve confirmed that this is currently expected behavior for copy/paste, as well as cut/paste of an unpublished component.

When we cut a component from fileA, we delete the component in fileA. If the component is pasted in another fileB and republished, two things can happen:

• if the component was originally published from fileA, the server will see that the component has been “moved” to fileB, so once it is republished in fileB, fileA will see it has updates to accept to relink the instances to the new published version from fileB
• if the component was not published in fileA (which is the case I was describing), pasting in fileB will not count as a “move” and the instances won’t receive updates and the backing component will remain deleted.

I hope this information helps clarify, but please let me know if you have taken different steps or if you habe any other questions!

Thanks,
Gayani

Hello,
I am experiencing the same issue in 2 of my projects, but after moving my master component from one page to another in the same files. What can cause that and how can I resolve it? Thank you

Hey @Isabelle_Langlois, sorry for the issues!
Could you try opening your working file and running a Quick Action called “Repair Component Connections”? 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.
I’ve included some instructions on running the command below.

1. Open the affected file
2. From the main dropdown menu in the top left, navigate to the “Quick Actions” search bar.
3. Search for “Repair component connections”
4. Run this command

Please let me know how it goes.

I don’t know if it helps, but for me it worked “Relink instances to local component”.