[Bug] HTTP 503 "Capacity Exhausted" Loop: Clicking "RETRY" locks out the entire account on Ultra Plan (€275/m)

Google Antigravity
1

I am currently on the Ultra plan (€274.99/month), having just moved out of the trial, and the service is completely inaccessible. It’s been like this for days.

I am sitting at 0% available usage for Claude (and other models) without even successfully prompting them. All I did was click “RETRY” after the agent failed a prompt. Instead of actually retrying, the system seems to register the server-side failure as actual quota usage, completely locking me out.

This is clearly a backend issue where HTTP 503 Service Unavailable errors are bleeding into the user’s quota limits. Paying for the top-tier plan to be met with “No capacity available on the server” and having my account penalized for server crashes is unacceptable.

Here are the network logs proving the 503 errors (Trace IDs redacted for privacy):

Error Log 1 (Gemini):

JSON

Trajectory ID: [REDACTED]
Error: HTTP 503 Service Unavailable
Sherlog: 
TraceID: [REDACTED]
Headers: {"Alt-Svc":["h3=\":443\"; ma=2592000...], "Content-Type":["text/event-stream"]}

{
  "error": {
    "code": 503,
    "details": [
      {
        "@type": "type.googleapis.com/google.rpc.ErrorInfo",
        "domain": "cloudcode-pa.googleapis.com",
        "metadata": {
          "model": "gemini-3.1-pro-high"
        },
        "reason": "MODEL_CAPACITY_EXHAUSTED"
      },
      {
        "@type": "type.googleapis.com/google.rpc.RetryInfo",
        "retryDelay": "52s"
      }
    ],
    "message": "No capacity available for model gemini-3.1-pro-high on the server",
    "status": "UNAVAILABLE"
  }
}

Error Log 2 (Claude):

JSON

Trajectory ID: [REDACTED]
Error: HTTP 503 Service Unavailable
Sherlog: 
TraceID: [REDACTED]
Headers: {"Alt-Svc":["h3=\":443\"; ma=2592000...], "Content-Type":["text/event-stream"]}

{
  "error": {
    "code": 503,
    "details": [
      {
        "@type": "type.googleapis.com/google.rpc.ErrorInfo",
        "domain": "cloudcode-pa.googleapis.com",
        "metadata": {
          "model": "claude-opus-4-6-thinking"
        },
        "reason": "MODEL_CAPACITY_EXHAUSTED"
      }
    ],
    "message": "No capacity available for model claude-opus-4-6-thinking on the server",
    "status": "UNAVAILABLE"
  }
}

Steps to Reproduce:

  1. Experience an agent error or failed prompt.

  2. Click “Retry”.

  3. Receive a 503 server error (as shown in the logs).

  4. Watch as the system incorrectly counts the server-side failure against the user’s quota, eventually locking the account out of all models.

Can an engineer please investigate how 503 errors are being handled in relation to user quotas? This loop is making the Ultra subscription completely unusable.