Instance ignores component's rotation

Hi Figma community,

I’ve just encountered this problem where the instances of rotated component appear without rotation when I drag them from the sidebar/search.

For example, I have these sticky notes that I leave around the files. They are both rotated for 4°. I used to import the instances through “Shift + I” menu and they would always appear the same as their original components. Now, however, they appear almost the same, sans the 4° rotation and I can’t figure out why.

Check out the video for reference.

This used to work fine until… today?
Anyone else having similar issues? Or any ideas on how to fix it?

Best regards,

1 Like

Hey @Kelly_Ne, thank you for reaching out. Appreciate that you’ve attached a screen recording!

Is it happening in the browser, desktop app or both? I wasn’t able to reproduce this issue on my end.

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.
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 fixes the issue. Alternatively I can ask the team internally for further help.

Hi @Gayani_S

Thanks for taking a look. Unfortunately, none of your suggestions worked.
All my files are affected by this, including the design system file.

In your case, you just created one component with one element inside. In my case, it’s a component set with variants inside being rotated. I’ve recreated the issue where I created two rectangles, without rotation, turned them into a component set, then rotated them, and when I called them from the Resources, they appeared without a rotation.

Here’s another video:

I can swear it didn’t work this way before, but maybe it’s a part of some new behavior in the code? If that’s the case, then I guess I have to make peace with that, but it would affect a lot of different components for a lot of various users, so I don’t think it’s a best decision.

Thanks for trying out these steps, @Kelly_Ne!
Apologies I’ve totally missed the part that you’ve created first the component set.

Yes, I am able to experience this issue on my end with these steps as well. This might be a potential bug.

I’ve just created a support ticket on your behalf. Your ticket number is #934853, for reference. I think our technical support team is able to dig further.

Thanks for flagging this, let me know if you have any further questions. Someone from support will be in touch with you soon.

Quick update: this issue resolved itself after a few days. Unsure whether Figma support or devs did anything, but they did their best to help.

Thanks :wave:

Hey @Kelly_Ne, glad to hear the issue got resolved! Thanks for giving me an update!