Internal error encountered (500) and can't send message because channel is full (Gemini 3.1 pro)

Hi,

When I start working, it seems to go well, but as time goes on, it becomes impossible to work.

It simply freezes, doing nothing or responding to me.

With my plan (Google AI Ultra for Business), it shouldn’t be like this. Unable to use the Gemini Pro model, I keep getting the following errors: Trajectory ID: xxxxxxx
Error: HTTP 500 Internal Server Error
Sherlog:
TraceID: xxxxxx
Headers: {“Alt-Svc”:[“h3=\”:443\“; ma=2592000,h3-29=\”:443\“; ma=2592000”],“Content-Length”:[“109”],“Content-Type”:[“text/event-stream”],“Date”:[“Mon, 23 Feb 2026 14:18:06 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=92073”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“f5329e39b0aadb7 0”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“mistake”: {
“code”: 500,
“message”: “Internal error encountered.”,
“status”: “INTERNAL”
}
}

Also in the terminal in Output-Antrigravity it keeps giving me the following message

25852 interceptor.go:74] /exa.language_server_pb.LanguageServerService/SendActionToChatPanel (unknown): can’t send message because channel is full

, which seems to indicate that it must be overloaded or something like that. I don’t know what to do anymore. I pay quite a bit of money for an account I can’t work with. The Ultra account is supposed to have priority over the others, but I simply can’t use it. Does anyone know a way to contact Google directly, or to get them to look into this specifically?

2 Likes

We’re starting the week with the same problem; I can’t use the Gemini 3.1 Pro model. This is relentless; the 500 error is persistent. Anything I ask it to do results in a 500 error. Can’t you notify technical support to fix this? It’s an AI Ultra Business account, and it’s quite expensive to use. It’s outrageous that this is happening.

1 Like

The same here, after the models have been updated to Gemini Pro 3.1, it’s not possible to use agents in the Antigravity - completely useless …

Same error, but different experience. I haven’t used anti-gravity in a couple weeks, because gemini was either VERRRRY slow (about 10 minutes to get a response to “are you there”) with crashing or completely non-responsive. Went into it today to see if it was working again, updated, and just get this response:

Trajectory ID: xxxxx
Error: HTTP 500 Internal Server Error
Sherlog:
TraceID: xxxx
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“109”],“Content-Type”:[“text/event-stream”],“Date”:[“Mon, 02 Mar 2026 13:43:45 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=2323”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“xxxxxx”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 500,
“message”: “Internal error encountered.”,
“status”: “INTERNAL”
}
}

Thank you for bringing this to our attention. We have escalated the issue to our internal teams for a thorough investigation.

To ensure our engineering team can investigate and resolve these issues effectively, we highly recommend filing bug reports directly through the Antigravity in-app feedback tool. You can do this by navigating to the top-right corner of the interface, clicking the Feedback icon, and selecting Report Issue.

1 Like

Hello All.

i have the same issue as well. it happend inthis latest update
i thought at he begining it was an authentinfication problem but after reinstalling antigravity , the error persist and show nothing have changed after reinstalling
Trajectory ID: d75f4e38-d352-4788-b448-…
Error: HTTP 500 Internal Server Error
Sherlog:
TraceID: 0x841393b59f3…
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“109”],“Content-Type”:[“text/event-stream”],“Date”:[“Tue, 03 Mar 2026 11:55:56 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=622477”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“841393b59f399144”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 500,
“message”: “Internal error encountered.”,
“status”: “INTERNAL”
}
}