Don't stop here
Hand-picked guides our readers explore right after this one.
Unlock Google's Gemini with multimodal prompting strategies
Read the guideExpert guide to Claude prompts with XML tags, artifacts, and complex reasoning
Read the guideAI prompts for bookkeeping, tax planning, financial analysis, and audit preparation
Read the guide'Something went wrong (1076)' (and its close cousin 1096) is Gemini's generic failure code, and the key thing to understand is that it does not have one cause. At least four distinct triggers produce this same number, which is why one person's fix does nothing for someone else. The most common is a temporary communication problem between your device, browser, Google account, and Gemini's servers. The one people miss is context exhaustion: a very long chat, especially one heavy with code or large pastes, can hit token limits and fail with 1076 rather than a clear 'chat too long' message. Work through the fixes in order below, and try the mobile-app workaround if the desktop thread stays stuck.
'Something went wrong (1076)' appears instead of a response
Error 1096 shows in the same situations
One long chat fails every time while new chats work
It started after pasting a large block of code or text
The error persists across refreshes on the same thread
The most frequent trigger: a transient break in the chain between your device, browser session, Google account, and Gemini's servers. These clear with a refresh or a re-login.
A very long conversation, particularly one loaded with code or large pastes, can run out of context. Gemini surfaces this as 1076 rather than a clear message about chat length, which is why it looks like a bug rather than a limit.
Stale cached data and interfering extensions (ad blockers and privacy tools especially) can break the request that loads a response.
A restrictive network, a VPN, or a stale Google account session can block the request. Signing out and back in forces a fresh session.
When to try: First, always
Reload the page and confirm your internet connection is stable. A large share of 1076 errors are transient and clear on a simple refresh. Test another site to rule out your network.
When to try: When one specific long chat keeps failing
If the error only hits one long conversation (especially one with lots of code or big pastes), that thread has likely exhausted its context. Open a new chat and carry across only what you need, or ask Gemini to summarize the thread first and paste that summary into the new chat.
When to try: If a refresh did not help
Sign out fully, then sign back in. This refreshes the account session between you and Gemini's servers and resolves the session-state version of this error.
When to try: If signing out and in did not clear it
Clear your browser's cached data and cookies for Google domains, close and reopen the browser, and sign back in. Stale cached data is a common cause when the error appears suddenly after everything had been working.
When to try: To isolate an extension conflict
Open Gemini in an Incognito or private window, which runs without extensions. If it works there, an extension is the culprit (start with ad blockers and privacy tools). Also make sure your browser is up to date.
When to try: When one thread stays stuck on desktop
A workaround users report: open the same chat thread in the Gemini mobile app, send a short message there, then go back to your computer and send your prompt again. This can unstick a thread that keeps returning 1076 on desktop.
When to try: If it fails across browsers and devices
Try a different network (mobile hotspot rather than corporate Wi-Fi) and turn off any VPN. Then check whether Gemini is having a wider incident before spending more time on local fixes.
Do not let one chat grow enormous, especially with repeated code pastes, start fresh threads for new tasks
Keep your browser updated and allow-list Google domains in ad blockers
Sign out and back in occasionally if you keep long-running sessions open
Paste only the code or text you actually need Gemini to see
If 1076 or 1096 persists after refreshing, a fresh chat, re-login, a cache clear, and testing without extensions, send feedback directly through the Gemini app. That is the route Google uses to investigate backend causes, and it carries your session details automatically. There is no faster support path for this error.
It is a generic failure code with at least four different triggers, most often a temporary communication problem between your device, browser, Google account, and Gemini's servers. It can also mean the chat ran out of context. Because the causes differ, work through the fixes in order rather than assuming one cause.
That pattern usually means the conversation has exhausted its context or token limit, which is common in very long chats loaded with code or large pastes. Start a new chat and carry across a summary rather than the whole thread.
They appear in the same situations and are reported together by users. Treat them as the same generic failure and apply the same fixes: refresh, fresh chat, re-login, clear cache, disable extensions.
Yes. Open that same chat in the Gemini mobile app, send a short message there, then return to your computer and retry your prompt. Users report this unsticks a thread that keeps returning 1076 on desktop.
Usually not. It is most often local (session, cache, extensions) or a context limit. Check for a wider incident only after refreshing, re-logging in, clearing cache, and testing in Incognito.