Hi ​@Dennis_N, 

Thanks for flagging this. To help us investigate further, could you please clarify what you mean by "Tag"? I'm trying to reproduce the issue, but I haven't been able to do so yet.

Thanks!

Toku

​@y_toku Sure! I looked further into that issue and realized that it seems to only happen to annotations attached to nested instances. Once fully detached, the tag won’t dissappear. 

Before I have copied them over to another file:

After

we’re seeing the same problem with the category disappearing when copy and pasting 

Hi ​@Dennis_N ​@Jayne_Vidheecharoen 

Thanks for clarifying! We haven't been able to reproduce this issue yet. Could you share the video recordings? Here's my test, and I'm not seeing it.

Thanks for your patience!

Toku

​@y_toku thanks for trying to reproduce.

Heres a video/gif:
 

• Both components - the button and its nested icon - are coming from 2 different linked files. They are no local components. Although it seems to make no difference anyway, as I can reproduce that bug with freshly created local components aswell.
• If I copy ’n’ paste the broken annotation with missing tags again back to the original file, the tags are visible again as you can see in the video.
• I’m on Windows 10 but was able to reproduce on latest MacOS 15.3.1 aswell
• Happens both in the figma app and browser(s).
• All of my applications are up to date.

Fingers crossed, that you or a colleague can reproduce and fix that bug.
Please reach back, If I can support further.

Dennis

​@Dennis_N Thanks so much for sharing the details! Let me investigate and will get back to you once I have any updates.

Toku

Hey ​@Dennis_N 

I could reproduce it, so shared internally: 

. 

Please know that our product team is currently prioritizing Config. Because of this, I can't give you a definite timeline for when a fix might be available. However, I will definitely reach out as soon as I have any updates I can share with you!

Thanks for your patience.

Toku

Hi all, 

Thanks for your patience. Our team released a fix for this, so it should be resolved! If you still see this one, please feel free to let us know. 

Really appreciate your flag and patience!

Toku

Hi Toku, I have not replied immediately because I thought the fix was not released yet or at least did not reached me but even a few weeks after your post the issue persists on my end. So unfortunately I can not confirm that the bug was fixed.

​@djv Sorry for bothering you but due to your activity on the forums I just ping you now. Could you please look into this issue as it still seems to be present to me and my team. Thank you in advance 

Hi ​@Dennis_N, thanks for following up and looping me in! 

I just tested this on my end, and it does seem to be fixed for me. Are you able to share your file with our support team here? https://help.figma.com/hc/en-us/requests/new

Our technical quality team may be better suited to do a deeper dive into what’s happening with you one one one. 

Thanks, I reached out to the technical support. In the meantime I found out that this bug can’t be reproduced within freshly created files (“post fix”). Older filed, created before figma launched the fix (“pre fix”) still have this issue. Unfortunately the majority of files we are working in were created before.