Skip to main content
Marc0
New Member
July 20, 2026
Solved

Copy Interactions not working properly

  • July 20, 2026
  • 24 replies
  • 479 views

Since Friday 16th of July the way I copy paste interactions is not working anymore. I normally would left-click on my noodle and press Ctrl+C and paste it into another object with Ctrl+V. The behavior is erratic, but mostly the whole object gets pasted onto the Frame instead of the interaction.

 

I have already 

  • cleared Desktop Cache
  • tried it in new files
  • tried with other accounts
  • tried on another PC

It’s really annoying for complex prototypes with lots of if/else interactions. 

Best answer by Tom Reem

Hello again! Good news — I touched base with the Technical Quality team, and Engineering has pushed a fix that should resolve this issue. ✅

If you haven't already, please close and reopen your files. After that, copying interactions should work as expected.

Thanks again for your reports and your patience while we followed up on this — and don't hesitate to reach out with any other questions or feedback.

24 replies

Tascha
Active Member
August 4, 2026

Chiming in here to say I have the same issue as well; it pastes my last copied text or item instead of the interaction. Not sure since when since it’s been a while I’ve worked with prototypes but can confirm it’s not working for 2 days for me now on the latest version 126.7.10 on windows desktop app 😑

Prasad Nagbhushana
New Member
August 4, 2026

Please fix this ASAP… its driving me nuts…. Basically i have keep linking same stuff again and again… If the elements are far apart dragging the link arrow is very tedious…. copy and paste is the perfect way….

 

Please make sure in future wen you release test the core functionalities. This will affect a lot of people….

Tom Reem
Figmate
Figmate
August 4, 2026

Hey ​@Rick Tilghman and ​@Pencilixel — thanks for the followups, and I'm sorry this is still getting in the way of your work.

I've flagged these reports internally, and am escalating to our Technical Quality team so they can dig into more specifics.

For anyone else following this issue here, the biggest thing that would help us reproduce it is a file where this is happening. If you haven’t already shared access, please run though the following:

  • Open the Support Hub → click Start a chat → type "Report a bug"
  • Share the affected file with support-share@figma.com with view access

With that, it will open up a secure case where our team can take a deeper dive. A note on your OS and app version (like the details ​@Tascha already shared) helps too. I'll keep watching this thread for additional reports, and get back with more updates as soon as I uncover more information.

Tascha
Active Member
August 6, 2026

​@Tom Reem ok I was able to boil it down (at least for me) to interactions that contain a change to interaction; the file page to mess around in for anyone interested: 

 

I’ll also open up a bug report now 🫤

 

Silvia Gamboa
New Participant
August 7, 2026

I just created my report #2058572

 

Please everyone, create a report so they can see that this is a real issue!

  • Open the Support Hub → click Start a chat → type "Report a bug"
  • Share the affected file with support-share@figma.com with view access
Tom Reem
Figmate
Figmate
August 9, 2026

Thank you both so much for taking the time to do that, ​@Silvia Gamboa and ​@Tascha — and for narrowing down when it happens and sharing a file to reproduce it.

Confirming we've received both of your reports and passed the details along to the Engineering team so they can dig deeper into what's happening. I'll keep watching this thread and relay any further reports. If the Technical Quality team needs anything else to reproduce it, they'll follow up through your support ticket.

Thanks again for sticking with us on this.

Tom Reem
Figmate
Figmate
August 16, 2026

Hey folks, just checking in to confirm our Engineering team has this on their radar and is looking into the reports we've received. Please continue to let us know if anything changes on your end, and we'll come back to this thread as soon as we have more to share.

Tom Reem
Figmate
Tom ReemAnswer
Figmate
August 19, 2026

Hello again! Good news — I touched base with the Technical Quality team, and Engineering has pushed a fix that should resolve this issue. ✅

If you haven't already, please close and reopen your files. After that, copying interactions should work as expected.

Thanks again for your reports and your patience while we followed up on this — and don't hesitate to reach out with any other questions or feedback.

Tascha
Active Member
August 20, 2026

Hello again! Good news — I touched base with the Technical Quality team, and Engineering has pushed a fix that should resolve this issue. ✅

If you haven't already, please close and reopen your files. After that, copying interactions should work as expected.

Thanks again for your reports and your patience while we followed up on this — and don't hesitate to reach out with any other questions or feedback.


I just tried, then tried again after also closing Figma alltogehter and still no dice; same behavior as before see video 😕

https://www.dropbox.com/scl/fi/mzaixelg8wi18c17zyrme/Figma_0dPV0eXD3S.mp4?rlkey=ydxfru80pdeqa5fotsoi7f9ft&st=02dipk9q&dl=0

The frantic flashing of the right element is caused by me repeatedly pressing cmd + c btw 😅

(fyi I will eventually delete this video from my dropbox, but it will stay as long as I have some space left 😅 which will be at least for a month)

Marc0
Marc0Author
New Member
August 21, 2026

It’s working on my browser setup again, so thanks for the ongoing support and the fixing. 😎