You are 12 messages deep into a debugging session. Gemini has your whole function, your error log, and the half-finished fix. Then it stops answering — and every message you send comes back as one line: Something went wrong (1099).
Refresh the app and it is still there. Reopen the chat: still there. On Android, 1099 has a habit of following you around for days, and it is the error people report when they engage Gemini with "Hey Google." Alike error can also be fixed at Gemini 1155 bug fix.
This guide covers what Gemini error 1099 actually is, how to tell in 60 seconds whether the problem is your device or Google's backend, and which fix to apply depending on where 1099 shows up.
What Is Gemini Error 1099?
Gemini error 1099 is a server-side session problem — not something you did to your prompt. Google has not published a public definition for it, so the most reliable description comes from Google Product Experts answering in the official Gemini Apps community: 1099 is a backend-specific error, reported as a server-side session conflict or "context overflow" on Google's end.
The user reports cluster around the same three triggers:
- A failed session handshake. One widely shared explanation describes 1099 as an authentication collision — if the handshake between your OS and Google's service layer is even slightly out of step (often right after a system update), the request is discarded and the app gives up.
- Long conversations. 1099 is repeatedly reported in long sessions, which is what "context overflow" refers to: the session state breaks and every new message in that thread keeps failing.
- Android and voice. 1099 shows up far more on Android than on the web, and several threads describe it specifically when starting Gemini with "Hey Google." There is also a version of 1099 that no fix on your side will solve. Google's own status dashboard has logged an incident in which "Gemini App (Web and Mobile)" users experienced a 50% error rate when attempting to send prompts, receiving "Something went wrong" messages. If that is the outage you are in, you are waiting it out, not fixing it.
Step 1: Is It You, or Is It Google? (60-Second Triage)
Answer these four questions before you change a single setting. They decide which section below you should read.
1.Does it fail on a second device too? If your phone and your laptop both throw 1099, the problem is your account or the backend — stop resetting the phone. 2.Try a private/incognito window with extensions disabled. The official community thread recommends this first, because it disables every extension at once. Works there? It is your browser profile. 3.Check the Google status dashboard for an active incident before assuming it is your setup. A documented outage beats any local workaround. 4.Note when it fails. Fails on the very first message = session or account. Fails after 10+ messages = context overflow. Fails only on voice or only in the app = Android-side.
Step 2: Apply the Fix That Matches Your 1099
The single safest way to troubleshoot 1099 is to match the workaround to the specific way the error is appearing. Start with the section that describes your situation.
A. It fails on the web, on every message 1.Private window, extensions off. If Gemini loads there, an extension is interfering. Disable them one at a time. 2.Clear cache and cookies for gemini.google.com only. Do not wipe your whole browser profile — target that one domain (chrome://settings/content/all → search for gemini.google.com). 3.Sign out completely, then sign back in. A stale session token produces 1099 on every send, and a clean sign-in is what clears it. 4.Switch network or DNS. Move from Wi-Fi to a hotspot, and set DNS to 1.1.1.1 or 8.8.8.8.
B. It fails only after a long conversation This is the context-overflow pattern, and it is the most common reason 1099 feels "stuck."
1.Start a new chat — do not keep re-sending into the broken thread. Every retry in a dead session is reported to keep it dead. 2.Shorten the session before it breaks. Ask for a summary of where you are, then continue in a fresh chat. Long threads of pasted code are exactly the shape that trips 1099. 3.Re-attach only what is needed. One function plus the error message beats the entire file.
C. It fails on Android, on a Galaxy, or with "Hey Google" This is the 1099 variant with the most reports — and the one where generic advice fails.
1.Reset the digital assistant toggle. In the Google app: profile icon → Settings → Google Assistant / Digital assistants, toggle it off, restart the phone, then toggle it back on. This is the most commonly reported workaround for 1099 on Android and Galaxy devices. 2.Clear cache and data for both apps, then reinstall if needed. Settings → Apps → Gemini → Storage → Clear cache, then Clear data; do the same for the Google app. If 1099 persists, uninstall both, reinstall, and restart. 3.Check what updated recently. Several users tie the first appearance of 1099 to a system or app update. If it started the same week an update landed, that is your likely cause — and the most reliable immediate workaround is to use Gemini in a browser until the next update.
D. It fails on every device, including a clean profile Stop hammering retry, and wait. If a second device and an incognito window both fail, you are in the backend group. Report it in the Gemini Apps community or check the status dashboard, and come back in a few hours. ★ When Gemini Locks You Out and You Still Have to Ship Here is the part 1099 makes worse than a normal glitch: it does not just fail one request, it can lock you out of the app entirely — for hours, sometimes days. Your deadline does not move with it.
The good news is that fixing the code and fixing Gemini are two separate jobs. You do not need a healthy Gemini session to get the bug in front of an AI model — you need a tool that takes the code directly.
AI Powered Coding Assistant Free is a free-trial coding assistant with a dedicated Fix Code task. Here is the whole workflow, four steps:
1.Open aipoweredcodingassistant.com and pick Fix Code from the eight tasks on the home page (Generate, Explain, Translate, Review, Fix Code, Regex, Diagram, Cron). Choosing the task up front tells the model to answer like a debugger, not like a chat.
2.Paste the code that is failing, plus the error message and what you expected to happen. Error text is not optional — it is the input that turns "rewrite this" into "fix this specific line."
3.Pick the model and generate. GPT, Claude Opus and Fable are all available in one place, so you can re-run the same broken function on a second model if the first answer misses.
4.Copy the result back into your project. You get the root cause, a corrected version of the function, an explanation of why the fix works, and a regression test that would have caught the bug in the first place.
That last point is worth the two minutes even when Gemini is working: it is the same job you were asking Gemini to finish when the session died. If you are not sure what is breaking in the first place, run Explain Code on the same snippet first — the same workflow we use in How to Turn Code to Flowchart from AI: understand the control flow, then fix the specific branch.
Because the assistant is model-agnostic, being locked out of one provider no longer stops your work. You change the model, not your toolchain. The free trial needs no credit card.
1099 Is Not Alone - The Something went wrong Code Family
Google does not publish a public mapping for these codes, so treat the table below as the pattern in user reports rather than documentation.
| Code | What the reports point to |
|---|---|
| 1099 | Backend session conflict / context overflow; heaviest on Android and "Hey Google"; can persist across devices |
| 1076 | Frequently reported alongside 1099 — one explanation is that the backend chokes with 1099 and the browser then times out with 1076 |
| 1155 | Session and network layer — most often linked to VPN / proxy traffic. We cover the fix order separately in Gemini Error 1155 |
| 1095 / 1096 / 1097 | Same symptom family — "Something went wrong" with no detail. The escalation ladder in this guide applies |
If you are chasing a different code, the sequence is the same every time: triage → session → device/app → network → accept that it is backend.
FAQ: Gemini Error 1099
What does "something went wrong 1099" mean in Gemini?
It is a backend session error. Google Product Experts describe 1099 as a server-side session conflict or "context overflow," not as a problem with your prompt or your code.
Why does 1099 keep coming back on Android?
Android is where 1099 is reported most, and it is frequently tied to the assistant layer — particularly when Gemini is started with "Hey Google." Resetting the digital assistant toggle in the Google app is the most commonly reported workaround.
Does clearing the cache fix Gemini error 1099?
Sometimes, and only if the cause is local. Work the triage first: if a second device throws 1099 as well, clearing anything on the first one will not help.
How long does Gemini error 1099 last?
If it is your session, minutes. If it is the backend, it can persist for hours or days across every device you own — during a documented incident, the error rate on prompt sending has been reported as high as 50%.
Can I still fix my code while Gemini is throwing 1099?
Yes — the error is on Gemini's side, not in your code, so the bug is still fixable. Paste the failing code and the error message into a dedicated Fix Code task on a different model, and you get a repaired version plus an explanation without waiting for the session to recover.
Is 1099 the same as 1076?
No. 1076 and 1099 are often reported together — the usual explanation being that the backend fails with 1099 and the request then times out as 1076 on the client side.
Summary
Gemini error 1099 is a server-side session failure. If it hits on a second device too, it is not your setup — check the status dashboard and wait it out. If it is local, match the fix to where it appears: incognito and a clean sign-in for the web, a fresh chat for long sessions, and the digital assistant toggle reset for Android and "Hey Google."
And when 1099 locks you out but your deadline has not moved, separate the two problems: Gemini is broken, your code is not. Paste the failing code and its error into Fix Code at aipoweredcodingassistant.com, pick a model, and keep shipping.
