Skip to main content
Prateek Tiwari
New Member
July 14, 2025

Bug: Figma Make shows "Try again with fewer inputs" even for short prompts after a few successful ones

  • July 14, 2025
  • 44 replies
  • 2069 views

I've been experimenting with the new Figma Make feature and noticed a recurring issue that's affecting usability:

  • After about 8–10 successful prompts (each 1–2 lines long), Figma Make starts rejecting any further prompt with the message:

    "Try again, with fewer inputs."

  • This happens even when the prompts are extremely short, e.g., "Create a dark-themed button component" or "Add a CTA section with three buttons."

  • I’ve tested this across multiple projects and browsers. The issue persists consistently, and the only workaround seems to be refreshing the tab, which sometimes helps temporarily — but not always.

Additional Context:

  • Even though Figma Make is currently laggy while generating prototypes (which I can overlook), this input rejection bug makes it difficult to iterate quickly or finish design ideas.

  • It feels like a silent rate-limit or session exhaustion issue that’s not clearly communicated to the user.

This topic has been closed for replies.

44 replies

Hideki uxer
New Member
July 16, 2025

Hi there, still with problem with my make file. Is there any workaround to do or check inside the code to revert the problem? Don’t know almost nothing of react apps … I’m really frustrated, maybe I’ll move the project to another tool like lovable, since I got the design file

LorraineSc
New Member
July 17, 2025

Hi there,

Any update on this? Still an issue for us and massively impacting. Any timeframe for a fix?

Cheers

Lor

 

Hi there,

Thanks for your comment. We're still investigating this. We'll let you know when we have an update. Sorry for the inconvenience!

 

VShkrom
New Member
July 17, 2025

Same problem for me. Also can’t finish my prototype in time before the planned demo.  I have pretty long and complex Make prototype and thought it is related to the silent limit of some kind. Also can’t add any prompt - even a very short and simple one like “rename text from A to B”.

If it is related to AI context then it would  be awesome to have a way to refresh it or build up in a new file using previously created code. 

Thank you

Gayani_S
Figmate
Community Support
July 17, 2025

Hey everyone, I’m really sorry to hear that this issue is still happening, especially after the fix was rolled out. I completely understand how frustrating this must be, and I want you to know that your feedback isn’t being overlooked.

I’ve flagged this again with the team and confirmed it’s being actively investigated. I’ll be keeping a close eye on this and will share any updates as soon as I have them.

Thanks so much for your continued patience — we really appreciate it.

Sanchay_Raj
New Member
July 17, 2025

I  have been facing this issue continuously for the last 2 days & it’s getting frustrating. When is Figma Team resolving this? __/\__

AlS
New Participant
July 17, 2025

it just started working again for me.  Thanks.

 

VShkrom
New Member
July 17, 2025

I’m still facing the problem. Started to work with a different prototype - works fine because context is new. My main prototype still cannot change any prompt. Looks like it is still in development

AlS
New Participant
July 17, 2025

I’m still facing the problem. Started to work with a different prototype - works fine because context is new. My main prototype still cannot change any prompt. Looks like it is still in development

I'm going to attempt the migration workaround now that it's working again before it stops working.  

 

Anyone have succes moving the project from Make to Cursor or VSCode?

Andrea_Braccaloni
July 17, 2025

Make is back for me! Yay.

 

thanks guys.

Tom Reem
Figmate
Figmate
July 20, 2025

Hi everyone,

I wanted to share an update after checking in with our engineering team — they’ve resolved this issue and will keep monitoring closely for any related problems. ✅

Huge thanks to everyone who flagged it and for your patience while we worked on the fix. If you notice anything unexpected or similar popping up again, please let us know.