Long loading times for Swap Instance panel

Ask the community
#1

Hey, I noticed that the Swap Instance panel in the Design tab takes a lot of time to load. No matter the internet connection (slow or fast) this take ages. Sometimes I need to restart Figma in order to make it work.

Some of the libraries, like this one: Phosphor Icons added to the Community, has more than 4,000 components
image

Not sure what is the technical strategy for serving components from the libraries but this is really slowing down my workflow (alongside the new, and messed up, way of not look-up for components among all the libraries).

2 Likes
#2

Following this as I’m experiencing the same issue, except it has stopped working for me and doesn’t load.

#3

Can also confirm same issue.

#4

Sam issue here

#5

Yes, this is a huge time suck as I have tried restarting Figma, my computer, disconnecting and reconnecting VPN, SSO, Logon, etc…

#6

Same here! Happens remotely (some files are fine, some long).

#7

Same issue here!

#8

Same issue :confused:

#9

I am having the same issue with the issue of the instances not loading at all…

#10

Hi! Exactly the same issue for me too!

#11

Yes, same issue here too.

#12

Ys, same issue here too

#13

I just closed Figma, and re-opened. Solved issue and able to load swap instance panel without delay.

1 Like
#14

same issue. solved this by using figma in the browser.
Reopening the Figma desktop does not work.
seems Figma desktop has an unstable connection?

#15

Same issue here! Loads indefinitely even on local components

#16

any solution found here?

#17

Hi everyone, this started suddenly for me and I can’t get the instance list to load no matter what I do on desktop app or the browser. Any help would be appreciated.

#18

Hi so I finally found a way around this by trial and error, I detached a copy of any component that has a swap instance property for a nested component. Then I tried loading the instance list for the component nested within the component we just detached and it worked. After that, the issue was resolved for nested components without the need to detach anything. Seems like the issue was to just get it to load once.

2 Likes
#19

Thanks @Hanan for the interesting discovery. Hopefully, it will help Figma find and fix the issue.

@Hiroko , I’ve also experienced just closing Figma Desktop and opening it again solves the issue for a day or two…

1 Like
#20

Can this be investigated officially please? Im experiencing this issue quite frequently.