A file can’t open with a tip "we experiencing issue open this file"

Hi everyone!

I’m trying to open a file, but it wont load. I have the same problem in desktop app and online. When I trying to open this file, I got this tip “we experiencing issue open this file”.

Can anyone help me? I need to open the file again.

I can open other files, but not that one.

Thanks in advance.

I tried to recover from historical versions, but the issue still persists.
I also tried to ask others to open this file, but still couldn’t open it.

I had met the same problem, and the file is still fail to open now…

Could anyone help me on this? The issue has greatly hindered my work!

I’m encountering the same issue here!

Hi there! Thanks for flagging this and sorry for the trouble here.

To start troubleshooting, please try to clear out the cache on desktop app and browser
And please try to use a different connection such as a hotspot if you are able to.

If this still doesn’t help, please reach out directly to the support team by reporting a bug: here

I see in the backend that some of you have already filled out a ticket. Please also make sure to include the console log (here’s the article how to export console logs), a link of your file, and add support-share@figma.com as an Editor, so they can take a closer look. Thank you!

After clearing the cache, this file cannot be opened either. I accessed Figma using Chrome browser. I also cleared the browser cache, but it’s still the same issue.

I have provided the address of my file via email. If there is any progress, please let me know.

Hey @yan_klaine , I see in the backend that the support team replied to you and your file is working now :slight_smile:

For visibility here, our engineers have shared an update that we just released a fix for this issue. As a workaround, please try restoring an old file version through the file browser.
You can follow the steps here:

Please let us know if you continue to experience any issues loading this file after refreshing Figma. You can report a bug here. Thank you!

Update: Good news, the issue is solved! Please refresh your tab.

Thank you for your patience while our engineers were investigating :pray: