Error messages

Something went wrong (1099)

Something went wrong (1099)

This is the line the Gemini app shows in place of an answer, on the web, in the Android and iOS apps and in Gemini in Chrome:

Something went wrong (1099)

The same threads are full of its twin, Something went wrong (1076), and one person saw (1096). We couldn't find a word from Google about what any of these numbers mean, and as of September 25, 2026 nothing in the Gemini Apps Help Center mentions them. So everything below comes from reading the Gemini Apps Community threads, where Product Experts answer (community volunteers, as James M. reminds people in his replies), and from what the people posting reported.

We counted nine English threads about 1099 and four about 1076. The two codes turn up together often enough that one post said any prompt "gives no response other than "Something went wrong (1099)" or "Something went wrong (1076)"", so they share this page.

June 10, 2026: an outage that looked like your account

On June 10 a wave of threads opened within hours. One of them collected about fifteen "same here" replies that day, in several languages, across the Fast, Thinking and Pro models. A company tech rep reported 1076 across every team, on old and new chats, even in an incognito window signed out.

Product Expert Rajat Patel posted the same reply in several of those threads: "Many users have reported experiencing this issue. It has already been escalated, and the team has confirmed that they are actively investigating and working on a fix." The next day the tech rep wrote that it was working again and Rajat confirmed it: "Yes, the issue is fixed."

So if the code appears on every chat, every model, every browser and a second Google account too, it's probably not you. Clearing your cache won't change a server-side fault. Send feedback (Settings & help, then Send feedback) and try again later.

One chat stuck while new chats work

The second pattern is narrower and it lasted longer. In a thread about 1076 in a specific chat, people in late July described the same thing: one older conversation refused every new prompt, new chats worked for a while, and temporary chats were fine. Product Expert James M. put it plainly on July 25: "Open a completely fresh conversation thread. The underlying model works fine, but the old conversation link is permanently stuck."

Two workarounds got more than one "this fixed it for me":

• Add the stuck conversation as a source in an empty NotebookLM notebook and open it from there. Two people replied that it fixed it for them.
• Copy your earlier prompts into a new chat and carry on there.

One poster's stuck chat started working again on its own after nearly a week. That's the part we didn't expect: nobody reported a fix from Google for this version, and Rajat was still telling people on July 26 that it had been escalated.

1099 during the "Analysis" step

For 1099 specifically, Product Expert Fred SR wrote on May 12 that it was "a known issue currently affecting some accounts during the 'Analysis' phase, particularly when the model is processing complex image edits or file modifications." Three days later he added that a free user on Flash had it too, so it wasn't limited to paid plans or the Pro model. A long-document user in another thread said almost all of their long working chats had stopped, and their workaround was to edit the previous prompt instead of adding a new one.

What to try, in order

Start a new chat with a one-line prompt. If that answers, leave the old conversation alone (or rescue it through NotebookLM). If it doesn't, try a different Google account in a private window: one person with 1099 in the power-button overlay found a second account worked, which points at the first account's state. If nothing works anywhere, it's the June 10 kind of day, and all you can do is report it and wait.