Blocking 429 & Crash Loop: Account-Specific "Missing Module" Error (Server-Side Flag Mismatch)

Google Antigravity
1

Issue Summary: I am an AI Ultra for Business subscriber. My account is globally blocked by a persistent RESOURCE_EXHAUSTED (429) error on all models.

Critical Diagnostic Timeline:

  1. Status: Issue started today on v1.15.8 and persists after clean install of v1.16.5. (1.15.8 was working)

  2. Cross-Account Test: A different Google account on this same machine works perfectly. This proves my local installation and network are fine.

  3. Session Behavior: The issue is not limited to a single stuck session. Every retry generates a new Trajectory ID, which is immediately rejected by the backend.

Technical Details:

  • Subscription: AI Ultra for Business

  • Error Log:

    Plaintext

    Error: model unreachable: RESOURCE_EXHAUSTED (code 429)
-- stack trace:
google3/third_party/gemini_coder/framework/generator/generator.(*PlannerGenerator).generateWithModelOutputRetry
...
Wraps: (3) model unreachable

Request: Is it possible to do a server-side reset of my account or something?. Since my UI shows 100% quota (Antigravity Quota Tracker idk how consistent this is) but the backend returns immediate 429s for new session IDs, my account appears to be desynced or stuck in a throttled state despite having zero recent usage.

4

Any updates here? Im’m so in the dark. Very frustrated, I’m sure it’s a bug, I know there’s not much I can do but I see nobody else is having this specific error.

5

I’m still blocked from using Antigravity…

Trajectory ID: 00416098-a199-....
Error: HTTP 500 Internal Server Error
Sherlog: 
TraceID: 0xb743b5b617...
Headers: {"Alt-Svc":["h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000"],"Content-Length":["109"],"Content-Type":["text/event-stream"],"Date":["Fri, 20 Feb 2026 14:38:46 GMT"],"Server":["ESF"],"Server-Timing":["gfet4t7; dur=138"],"Vary":["Origin","X-Origin","Referer"],"X-Cloudaicompanion-Trace-Id":["b743b5b61772be3"],"X-Content-Type-Options":["nosniff"],"X-Frame-Options":["SAMEORIGIN"],"X-Xss-Protection":["0"]}

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

Bumping, been 16 days and no fixes and little messaging/information has been made available.