Something went wrong (1185)
The message
Something went wrong (1185)What it means
One conversation stops answering while new chats work. Google hasn't said what 1185 means; a Product Expert says Google is aware of it.
What to do
Edit the last prompt that got a good answer and resend it, or branch a new chat from that reply. Copy anything important out of the chat first.
Gemini puts this where the reply should be. In most reports it then sticks to that one conversation, however often you retry:
Something went wrong (1185)Every forum thread we found about it opened between August 28 and September 1, 2026. People were still posting it on September 22.
What Google has said about 1185
Nothing public. Google doesn't document what Gemini's error numbers mean, and no Google employee answered in the five threads we read. A Silver Product Expert (a volunteer Google badges on its forums, not staff) wrote on September 3: "I understand that the team at Google is aware of the issue and is actively working on a resolution. I don't have any other updates."
Their earlier guess was that it "usually pops up on specific long threads when a temporary server-side glitch hits that specific chat history". Another volunteer, answering someone who was building a game in Gemini Flash, said it happens when a session "becomes too large or there is a temporary issue at the server end".
What seems to set it off
One chat dies while new ones work. One thread's title says it outright: "Getting error code 1185 on specific chat". A reply in the busiest thread put it bluntly: "that specific thread is what is broken, not your account."
Two users described what came before it. One saw it "when I stop an answer while is being generating multiple times, to modify the prompt". Another blamed a connection that changed while a response was still generating. Neither is confirmed. Both point at a last turn that never finished, and the fixes that worked all replace that turn.
How people got the chat back
Copy anything you can't lose out of the chat first. If it won't open, the Product Expert pointed to Google Takeout (pick only Gemini Apps) to download your history.
- Edit the last prompt that got a proper answer and resend it. One user: "now it works just fine after being stuck for the past 11 hours." Another found editing only worked "on a browser, since you can't do that on the app".
- Or hit retry on the last good reply, so the broken turn is regenerated.
- Or branch a new chat from the last good reply (three-dot menu). It carries the history up to that point. Renaming the old chat didn't help the one user who tried it.
- Last resort: one person downloads "the whole chat as PDF and then give that PDF to a new chat so it has the conversational context".
If every chat throws it
Then editing won't help. One poster wrote: "This has been happening in all my chats when I click retry." Send feedback from inside the app and wait. We expected Google to say something by now; three weeks in, a volunteer's "the team is aware" is still the only word.
For 1152, which tends to hit long or heavy chats, see our 1152 page.