Antigravity Agent still failing with HTTP 429 RESOURCE_EXHAUSTED

Google Antigravity
1

Hello Antigravity Support Team,

I am still unable to use the Antigravity Agent because every request fails with HTTP 429 RESOURCE_EXHAUSTED.

The issue occurs even with a completely new conversation and a very simple prompt such as “hello”, so it does not appear to be related to my project, code, or prompt.

I have also tried different models, but the Agent terminates with the same 429 error.

My Google AI Pro subscription is active, and the Antigravity Model Quota screen shows available quota. However, the Agent still fails.

Latest error:

Trajectory ID: c7506ff3-8dc5-428d-8bd3-be7b5383ca..

Trace ID: 0x32c0c85c261d4a..

HTTP: 429 Too Many Requests

Status: RESOURCE_EXHAUSTED

Message: “Resource has been exhausted (e.g. check quota).”

Timestamp: Wed, 09 Sep 2026 05:19:40 GMT

This issue has continued even after the quota refresh period.

Could you please check the backend logs for this Trajectory ID and Trace ID and verify whether there is an account entitlement, quota synchronization, rate-limit, or backend service issue affecting my account?

I have attached a screenshot of my Model Quota screen showing the available quota.

Please let me know if you need any additional logs or diagnostic information.

Thank you.

2

Hi @Swapna_Karumoju,

HTTP 429 (Too Many Requests / RESOURCE_EXHAUSTED) errors indicate that your request volume has temporarily exceeded the per minute rate limits for your active model. But since this is happening even on a simple “hello” with a fresh conversation and your quota screen shows available quota, it feels like a synchronization issue.

If you haven’t already, could you double check that you’re on the latest version? Upgrading to the latest Antigravity 2.0 (v2.12.2) or the Antigravity IDE (v2.5.5) helps a lot because those updates have much better built-in retry and backoff handling for rate limits.

Also, sometimes logging completely out of the 2.0/IDE and logging back in can force refresh your quota and resolve any sync issues with your subscription.

3

Hi Veeranjaneyulu,

Thanks for the suggestions! Upgrading to version 2.12.2 resolved the issue for version 3.8, and it is working as expected now.

However, I am still encountering the HTTP 429 RESOURCE_EXHAUSTED error when using Gemini models from 3.1 to 3.6 (both high and low options).

Is there a specific fix or update required for these models as well? Please let me know how best to resolve this.

Regards,
Swapna

4

Hi @Swapna_Karumoju,

Thank you for upgrading and confirming that it works for version 3.8!

There are no additional updates or specific fixes required for models 3.1 to 3.6. I suspect this might be due to your weekly quota being exhausted for those specific models.

Could you please share a new Trajectory ID for the failing 3.1 -3.6 model requests so we can diagnose the issue?