Hi ​@Thageer , thanks for flagging this issue!
I see in the backend that you have already reached out to the support team, thank you! Can you please also add in your support ticket a link to the file, and ‘edit access’ granted to support-share@figma.com?

This won’t impact your billing and will help the team investigate more effectively.

I’ve also gone ahead and escalated your ticket internally. Thanks again for your patience while we look into this!

i have sent a mail with the link ( with edit access) to the above shared email address

​@Celine_ 

but the mail is not working

this was the reply:
We're writing to let you know that the group you tried to contact (support-share) may not exist, or you may not have permission to post messages to the group. ​@Celine_ 

Just to clarify, to grant edit access, click the blue “Share” button in your file, then add support-share@figma.com and set the permission to Can edit.

I also saw that the support team has replied to your ticket. I recommend continuing the conversation directly with them. They’ll let you know what additional details they may need to investigate further and help move things forward. Thank you 

 I’m currently in the same situation.
After 270 prompts, I’m stuck and Figma make won’t even perform simple requests, like change the text from the ui

exactly @will_remigio

at least they could have shown a usage limit indicator like other competitors. It's really frustrating when everything suddenly stops working without warning. I hope Figma resolves this issue soon or introduces a proper subscription model for the Figma Make product

Keep getting this persistent error since last night. “Something went wrong. Please refresh or try again later.” Unable to proceed with Figma make at all. 

​@balajiaiaik86  the problem with figma make as of now is…  its restricting the response (if the limit reaches nearly 300 version or close to these number)
i have raised a ticket .. i hope the tech team solves it soon :)

Hi all, thanks everyone for bringing this up!
As ​@Thageer mentioned, our engineering team is currently looking into it. We really appreciate you flagging it and your patience while the team investigates

I have the same problem, can you help me?

I have the same problem, can you help me?

While creating an app in Make the Claude chat interface grew gradually slower in its responsiveness and ability to update the app. Eventually prompts began to return the “Something went wrong error” no matter what I type in. It seems to be a result of longer message chains as I am up to version #374 of my app.

I am not sure how to proceed since the app is now just stuck at this point with no way to debug through the chat interface. The preview works fine, but I cannot do any more development. Have I hit some kind of cap in usage, memory or space? Please help.

When I switch to a new tab to create a new app, the responsiveness returns, as well as the ability make updates to the new app, but I need to finish the previous one.

I have tried creating a copy, resetting and restarting figma, duplicate quitting Figma processes running in the activity monitor and restarting my whole system, but the problem with the chat continues to exist. 

Thanks for any help you can offer. I am loving Figa Make otherwise! Really impressive!

"This post was merged into this topic from the original thread “Stuck in an endless loop of ‘Something went wrong’ in Figma Make” by a moderator on July 22, 2025.]

Hello! I'm having the same problem. I'm in the final stages of my prototype and had planned to finish it today, but I'm getting this error. What do I do now? I've done 340 prompts.

Hello everyone,

I checked in with our engineering team, and they’ve confirmed that a fix has been deployed for the error several of you have reported.

When you have a moment, please restart the app or refresh your tab. If you’re still seeing a “Something went wrong” message, please reach out directly and we can take a deeper look.

We’ll continue monitoring this thread for any further reports as well. Thank you again for flagging this and for your patience while we worked toward a fix.

This seems to have made the chat more responsive and cleared the hurdle of moving forward! Thank you for such a quick turn around! I’ve messaged you privately with the link to the dev area where you can see what I am building. - Paul

​@Celine_  I continue to have this problem and it has persisted for me for multiple days without any resolution. Can someone look into my project and try helping with a fix? I’ve copied the project, changed its name etc. but nothing is helping for multiple days already and its very frustrating.

Hey ​@GDS0X , thanks for flagging it! I see in the backend that you have already reached out to the support team, thank you!

They are waiting for your response to investigate it further, please check your inbox when you have a moment. Your ticket number is #1442457

Hello, All of a sudden last night my project has been non-stop “thinking” and then throwing up a Something went wrong error. I’ve done all recommended troubleshooting steps but no luck so far:

• Restarted session, log in/out
• Tried different team member’s account
• duplicated project 
• restored old versions where prompts were working before

Nothing is working and I’ve raised ticket 1452619 but no response yet, can someone please assist?

Hi Jared, thanks for reaching out and for trying those steps! I was able to locate your support ticket and the technical quality team has responded.

For visibility here: we’ve received similar reports from other users seeing this error in Figma Make files with large chat histories. Our engineers are actively working on a fix, and they have added your case to the investigation.

We really appreciate your patience in the meantime!

Hi everyone,
Sharing an update here regarding ​@Jared Goldberg ‘s case for anyone who encounters similar issues.  
The engineers have released and verified a fix for this issue. Please clear the desktop app’s cache by navigating to Help > Troubleshooting > Reset Figma and Restart. This will ensure you're using the latest release.
If the issue still persists, please reach out direct to our support team so they can investigate further your case here: Submit a bug report. Thank you!