Project-level page error: “Something went wrong” appears on specific files only

Additional context after checking the Figma Desktop app DevTools:

I inspected the console when the issue occurs.
There are no visible JavaScript errors or stack traces (no Uncaught, TypeError, etc.) at the time the editor becomes unresponsive.

The UI appears to stall at a loading/rendering state, and shortly after that the full-page
“Something went wrong. Our team is investigating.” error is shown.

This happens when performing normal editing actions (e.g. small edits or interactions), not just on initial load.
Rollback to earlier versions of the file also results in the same error.

This further suggests a server-side file state / history reconstruction issue, rather than a client-side runtime error.

I can provide Error IDs, file URLs, or additional reproduction details if needed.

“While reproducing the freeze in Figma Desktop (DevTools open), I consistently see a failing request: POST /api/make/fetch_ds_code_gen_status returning 400 (Bad Request) around the time the editor becomes unresponsive. There are no obvious JS exceptions/stack traces in console. This might be related to Figma Make / DS code gen state rather than a local runtime error. I can share exact timestamps/Error IDs/file URL.”

I was able to capture a concrete console error when the issue occurs.

When running a Make prompt on the affected project, the generation starts normally, but right near the completion stage (when the result seems to be applied to the file), the editor crashes with React error boundaries.

Console shows repeated errors such as:

• Uncaught TypeError: Cannot read properties of undefined (reading 'generating')

• Uncaught TypeError: Cannot read properties of undefined (reading 'renderRulers')

• getDerivedStateFromError

This happens only on specific projects and is reproducible.
Other projects work fine with the same Make prompts.

This suggests a case where the Make execution / commit state becomes undefined for certain file states, causing the editor to fail during the final apply/render phase.

I’ve attached a screenshot of the stack trace.
I can also provide file URLs, Error IDs, and reproduction steps if needed.

Update / Additional findings

I was able to narrow this down further.

This issue occurs only when using Figma Make (AI prompt execution).
Manual edits in the same file work normally without any problems.

When running a Make prompt, the generation starts as expected, but near the final stage (when the result is applied/committed to the file), the editor becomes unresponsive and then shows the full-page
“Something went wrong. Our team is investigating.” error.

Key points:

• File opens and renders normally

• Manual editing works fine

• The crash is reproducible only via Make AI prompts

• Rolling back to previous versions does not help

• Console shows errors like:

  • Cannot read properties of undefined (reading 'generating')

  • Cannot read properties of undefined (reading 'renderRulers')

• Around the same time, POST /api/make/fetch_ds_code_gen_status returns 400 (Bad Request)

This suggests an issue in the Make execution / apply (commit) pipeline for certain file states, rather than a general file corruption or memory-limit problem.

I’ve also reported this via the bug report form and shared the file with support for investigation.

Update:

I confirmed that this issue occurs even when using Figma Make on a brand-new empty page and an empty frame with the simplest possible prompt (e.g. “add a single text”).

In this file, Make generation starts normally, but the editor consistently crashes at the apply/commit stage when the result is being applied to the file.
Manual edits continue to work without any issues in the same file.
Make works normally in other files within the same account.

This fully blocks the use of Figma Make for this specific file.
Rolling back to previous versions does not resolve the issue, and duplicating the file results in iframe initialization failure.

Error IDs are generated consistently on each attempt.

Hi ​@baewadalmaster — welcome to Figma Forum, and thank you for taking the time to document everything so thoroughly. That level of detail is genuinely helpful as we look into what’s happening here.

A few issues affecting Figma Make output and performance were recently resolved, including one just yesterday. If you haven’t already, could you try fully restarting Figma and let me know whether things improve? Also, for the Figma Desktop App, can you confirm you’re running version 125.11.6 or later?

I checked in on your report and can see that our Technical Quality team is actively reviewing it now. Your case number is: 1707240, and they’ll follow up directly at the email tied to your Figma account once they’ve had a chance to take a closer look at the file.

Thanks again for the time and care you put into sharing this — we really appreciate your collaboration as we work to get this sorted out. Please don’t hesitate to reply with updates. 

Hi Tom, thank you for the update and for looking into this.

I’ve confirmed the following:
- I fully restarted Figma and re-tested.
- I’m currently using Figma Desktop version 126.0.4 (latest).
- The issue still reproduces consistently.

In this file, Make generation starts normally, but the editor crashes at the apply/commit stage.
This happens even on a brand-new empty page and frame with a minimal prompt.
Manual edits continue to work, and Make works normally in other files.

I understand the case is being reviewed by the technical quality team (Case #1707240).
Happy to provide any additional logs or reproduction details if needed.