Skip to main content
Question

Figma Make fails after 1084 prompts and shows “App.tsx is large and may cause errors”

  • January 14, 2026
  • 1 reply
  • 23 views

Kumar Sai Arja

I’m experiencing a recurring issue in a Figma Make project after extensive usage within a single project file.

In this project, I was able to successfully run 1084 prompts. However, when attempting to run Prompt #1085, the execution fails repeatedly. Each retry shows the following error message:

“Couldn’t connect, check your internet and try again”
(A new Request ID is generated each time.)

This happens consistently, even after multiple retries, and does not appear to be related to my local internet connection.

In the same project file, when I switch to Code Mode, the main file App.tsx displays a warning:

“This file is large and may cause errors.”

Because both issues occur together, it seems likely that the problem may be related to project size, accumulated prompt history, or generated code limits within Figma Make.
 

Questions / Help Needed

  1. Is there a limit on the number of prompts that can be run in a single Figma Make project?

  2. Is there a file-size threshold for App.tsx or other generated files?

  3. Can a large App.tsx file cause prompt execution or connection errors?

  4. Are there recommended best practices for long-running Make projects (e.g., splitting work into multiple projects or resetting history)?

  5. Is there a way to permanently resolve or prevent this issue without recreating the project from scratch?

  6. Are there any official workarounds or alternative workflows for large or complex Make projects?
     

Any guidance or confirmation from the Figma team or community would be very helpful

1 reply

ksn
Figmate
  • Community Support
  • January 30, 2026

Hey ​@Kumar Sai Arja 

  • Clearing / resetting the Make chat history can help in cases like this
  • A large App.tsx file on its own is unlikely to cause the connection error
  • Can you ask Figma Make to refactor and split code into smaller files? That could also help.

If it keeps happening, the next step is filing a support ticket so our teams can review further. If none of the above help, please fill out the help form here, and someone in support with be in touch. Thank you!