Error messages

Something went wrong (1152)

Something went wrong (1152)

This is the line Gemini puts where its answer should be, on the web and in the apps:

Something went wrong (1152)

On Android the same failure has shown up with a shorter number. The person who opened the busiest 1152 thread on Google's Gemini forum said their phone gave "the same error (with the number 11 instead)".

What Google says the number means

Nothing. Google doesn't document Gemini's numeric error codes anywhere we could find, and no Google employee had replied in any of the 1152 threads we read as of September 25, 2026. What there is comes from Product Experts, who are volunteers Google badges on its help forums. They aren't staff, and their answers read as informed guesses.

Those guesses do line up, though. A Silver Product Expert wrote in May 2026 that 1152 and its mobile "(11)" sibling "usually point to an issue with the backend communication between your account and the Gemini servers, rather than a problem with your local device." A Gold Product Expert in another thread tied it to "context token limits or account-sync glitches during heavy continuous chat sessions", and a second Gold Product Expert put it plainly in July: it "happens when your chat gets too long or hits an image limit."

The pattern in the threads

We read six forum threads about 1152. The same shape keeps coming back: one conversation breaks while others don't. One user wrote that a new chat clears it, "but after a while in the chat, the error 1152 will happen again." Another had a 20,000-word conversation behind it. People working in Canvas all day, or in notebooks, hit it most.

It isn't only long chats. Someone in June got it "after only one or two exchanges" on several accounts, and a user in Turkey saw 1152 alongside 1155 and 1099 every afternoon. When fresh chats fail as well, that points at Google's servers, which is what the Gold Product Expert concluded too: "The issue is likely server-side."

Getting the conversation back

If it's one chat that's stuck, don't delete it first. Copy out whatever you need. In the web app, the chat's export to Docs keeps the loaded part of the history (scroll to the top before exporting, since one user found it only covers what's loaded).

Then work around it:

• Retry the last reply once.
• If that fails, edit your last prompt and resend it.
• Branch the chat from the last reply that worked (the three-dot menu on a reply). A user recommended branching from before the errors started, and it keeps the history without the broken turn.
• Start a new chat and paste in the context you saved. This is what every Product Expert answer we read ended on.

A trick circulated in July (turn on image mode and start the prompt with "DONT GENERATE IMAGE, I WANT TEXT ONLY:"). Several people said it worked, but the person who later started a thread titled "error 1152" reported it stops working once an image does get made, so we wouldn't lean on it.

When a new chat fails too

Then there's nothing to fix on your device. Clearing the cache, switching browsers and turning off a VPN are worth one try each, but the forum posters who'd done all three still got 1152. Use Send Feedback in the app so the report reaches Google with your account attached, and try again later. We were surprised how many of these threads end without an answer from Google at all, so don't expect a reply on the forum.

Gemini shows other numbers in the same place. If yours is 1185 and it's stuck on one particular chat, see our page on 1185.