Error messages

Something went wrong (9)

Something went wrong (9)

This is the message you get where Gemini's answer should be. It's the same on gemini.google.com and in the apps:

Something went wrong (9)

There's no word from Google on what the 9 stands for. As of September 26, 2026 the Gemini Apps Help Center doesn't mention it, and nobody from Google has replied in the two community threads with this code in the title. The people answering there are volunteer Product Experts, and they can't see your account. So this is a pattern I pieced together from both threads, read in full on September 26, 2026.

It usually starts with a Docs or Drive link

The longest thread opened on November 25, 2025, and people were still adding to it in February. The first post sets the shape. Two prompts with a link to a Google Doc worked fine. After that, every question failed. A reload and a cleared cache did nothing (that's the first thing everyone tries, and in this thread it never helped).

Others described the same order of events, and they didn't all use Docs. One Pro subscriber said it "happened after sharing google docs link", and from then on text prompts failed in any thread using Pro features, though image generation still worked. Someone else hit it in a personal Gem (a saved custom version of Gemini) that read videos. A third only got it on Pro, when pasting long code.

What got people unstuck

The fixes that people confirmed all change the last request instead of repeating it:

• Edit the previous prompt and resend it. One user added a single period to the end of their last message and resent it. It answered, and it kept answering after that.
• Delete the Docs or Drive link from that prompt before resending. Product Expert Fred SR put this first in a "Community Cheat Sheet" he posted in the thread on December 22, 2025.
• Ask Gemini to research the topic again from scratch instead of asking it to carry on. The user who tried it said it worked.
• For a stuck Deep Research chat, one person switched the chat to Guided Learning, sent "test" a couple of times, and the 9 went away.

Fred's third suggestion was to turn off the Google Workspace extension under Settings, then Extensions, and try again. Nobody reported back on that one (so I can't tell you whether it works). He summed it up as "the error often lives in the history or the attachments of the active session". That fits what users saw. It's still his reading, with nothing from Google behind it.

Sometimes waiting was enough. The Pro subscriber above wrote the same day that "the thread just came back to live", and they had no idea why.

When it isn't one chat

A few reports don't fit the stuck-chat shape, and they're harder to fix. One person got 9 in Chrome on a computer and on a phone, while the Gemini mobile app worked on the same account. Another had it on every device and browser for days. For those, a second Google account on the same device tells you whether the problem is the account or the machine, and Send feedback from the failing account is the route every volunteer in these threads ends up recommending.

Product Expert James M. posted the same note in both threads (October and November 2025): Google's support team had reported a "Something Went Wrong" issue fixed and was rolling the fix out. It didn't end anything. New reports kept arriving into February 2026.

Is 9 a gRPC code?

Maybe. gRPC (the system Google's services use to call each other) numbers its errors, and in its table 9 is FAILED_PRECONDITION: the request "was rejected because the system is not in a state required for the operation's execution." That'd match a chat that's wedged on a bad attachment. In a thread about code 8, Fred SR called 9 a "permission/handshake glitch". But Google has never said the app's numbers come from gRPC, and I couldn't find anything that shows they do.