Figma Make - Unable to publish prototype update - "Something went wrong" error

Hi everyone,

Celyn from Figma Community Support here.

Our Engineering team has pushed a fix and confirmed that the issue has been resolved. Please refresh your files and let us know if you’re still experiencing any issues.

Thanks again for reporting this and for your patience!

My figma make file is not publishing yet.

Hey ​@Shubhangi , thank you for flagging this!
I was able to see your support ticket, and escalated it internally. The technical quality team is waiting for your response to investigate it further. Please check your inbox when you can (shxxxxxgi@gxxxxe.xxm), thank you! (For reference, your case number is #1718275)

I keep getting a ‘Update attempt was unsuccessful’ message any time I attempt to publish changes to me Figma Make project. It was working before but i started getting the error like 10 mins ago.

I am experiencing the same unable to update/publish issue. I tried restarting/relaunching eve tried to rollback some updates. yet the issue persists. and apparently its just with one file right now. Please Help

Hi everyone,
I’m facing the same issues, I’m not able to publish my project. Could you help me on this matter please? It is critical for me to have this feature working to continue my client delivery. 
Thank you in advance for your support.

Hello Figma Support Team,

I’m experiencing an issue where my site has stopped publishing and updating. Any changes I make are not reflected after publishing.

I tried troubleshooting by creating a new file and moving all pages there, but the problem still persists — the site does not update.

Could you please help me understand what might be causing this and how I can fix it?

Thank you in advance for your help.

Hi everyone,

I’m experiencing a publishing issue again and I’m trying to understand whether this is an isolated case or something broader.

For the past 3 days, I haven’t been able to publish any updates to my project. The publishing process fails every time. Support hasn’t responded for three days now.

Today I even temporarily disabled the entire backend (Supabase integration) to check whether the issue was related to runtime connections. I replaced everything with static data and tried publishing again — still no success.

So at this point it doesn’t seem to be a backend issue, but possibly something on Figma’s side.

Is anyone else experiencing publishing problems over the last few days?

Would really appreciate hearing if this is happening to others as well.

Thanks in advance 🙏

Hey ​@AnastasiaSv , Celine from Figma here.  Sorry for the delayed response, and thanks for your patience while this was being investigated.

I can see in the backend that your issue has been solved (you are able to publish correctly again). In this case, the failures were caused by invalid code in the Make file — specifically import/export errors in OpenAITestPage.tsx. After correcting those errors, publishing should work as expected.

For anyone else who might run into something similar: if publishing keeps failing even due to invalid code in your Make file, it can sometimes be due to validation errors inside a Make file. Checking for broken imports/exports (or prompting Make to fix them) can resolve it.

Appreciate you flagging this and sharing details here, it’s helpful for others who may encounter the same behavior!

For others, if you are still running into issues, feel free to submit a bug report directly so our support team can take a closer look at your case. To do that, go to the Support Hub / Click Start a chat / Type “Report a bug” / Include a direct URL to the impacted file. Thank you!

Hey everyone. Had this publishing issue occur for the first time for me now. I tried all the fixes that were discussed here but none of them work sadly. I also tried to duplicte the file, let colleagues try to publish it etc and nothing seems to fix this issue. Any other ideas on what I can do to be able to publish this file? 

All other files I can publish without a problem btw.

BR,

Julius

Hey ​@Julius von Ingelheim , thank you for trying the steps mentioned in this thread. I can see you’ve already reached out to our Support team. I can confirm that your case has been assigned, and I’ve added a follow-up note internally for visibility. For reference, your support ticket is #1752060.

As a heads up, we’re currently experiencing a higher ticket volume, so replies may take a bit longer than usual. Someone will be in touch as soon as possible. We appreciate your patience!

Thanks Celine. I finally found a solution with some deep digging in the file and this was the issue + solution (if anyone might try something similar as a fix):

Root Cause In vite.config.ts, resolve.dedupe includes three Lit sub-packages: '@lit/reactive-element', 'lit-html', 'lit-element' dedupe forces Rollup to resolve these from the project root of node_modules/. But with pnpm's strict layout, those three packages are never symlinked at the root — they only exist inside the .pnpm virtual store (at .pnpm/lit@3.3.2/node_modules/). During vite build, Rollup can't find them at the root and silently fails with no error output. The Fix Edit vite.config.ts — remove @lit/reactive-element, lit-html, and lit-element from the resolve.dedupe array

Glad to hear you were able to find a fix. Thanks for following up and sharing your solution with the community!