Persistent HTTP 429 RESOURCE_EXHAUSTED Error in Google Antigravity Across Multiple Accounts and Models
Hello Google Antigravity Team,
I am experiencing a persistent HTTP 429 – RESOURCE_EXHAUSTED error in Google Antigravity. The problem occurs across multiple Google accounts and multiple AI models.
Environment
-
OS: Ubuntu 24.04 LTS
-
Antigravity Version: 1.107.0
-
Electron: 39.2.3
-
Location: Pakistan
-
Google Accounts: 4 different Gmail accounts tested
-
Network: Normal internet connection, no VPN or proxy
Error
When I try to run an agent, Antigravity fails with:
HTTP 429 Too Many Requests
Resource has been exhausted (e.g. check quota).
Status: RESOURCE_EXHAUSTED
Code: 429
Server: ESF
Recent error details include:
Trajectory ID:
5a634ac6-10c7-4fed-9002-e91ee0fd3f..
Trace ID:
0x56c217860ca1e1..
I also tested another model and received the same error:
Trajectory ID:
9e00f48a-82ab-4823-8276-c867f98124..
Trace ID:
0xecbf753849ddc0..
Models Tested
The error is not limited to one model. I tested different models, including:
Both produce the same HTTP 429 RESOURCE_EXHAUSTED error.
Multiple Google Accounts
I have connected four different Gmail accounts to Antigravity. The problem occurs with all of them.
Therefore, this does not appear to be a problem with a single Google account or a single model quota.
Troubleshooting Already Performed
I have already tried the following:
-
Restarted Antigravity.
-
Completely closed and reopened Antigravity.
-
Checked the Antigravity processes.
-
Tested the Google Cloud Code endpoint.
-
Tested the Generative Language API endpoint.
-
Confirmed that the Google endpoints are reachable from my system.
-
Tested multiple AI models.
-
Tested multiple Google accounts.
-
Checked the available model quota.
-
Confirmed that the error continues even after restarting the application.
The network endpoints respond successfully, so this does not appear to be a basic connectivity problem.
Quota Information
The quota screen shows that the quota refreshes periodically, but Antigravity still returns RESOURCE_EXHAUSTED when attempting to execute an agent.
The important point is that the error occurs even when there is no obvious indication that the model itself is being exhausted.
Additional Symptoms
Before this issue, I also experienced:
-
“Connection to server got closed. Server will restart”
-
“Couldn’t create connection to server”
-
ECONNREFUSED 127.0.0.1:34845
-
Agent execution terminated
After restarting Antigravity, the application launches, but agent execution still fails with HTTP 429.
Request
Could the Antigravity team please investigate whether there is a backend quota/account entitlement synchronization issue or server-side RESOURCE_EXHAUSTED bug affecting Antigravity agent execution?
Since the problem occurs across multiple accounts and multiple model families, I believe this may be a server-side issue rather than a local configuration or project issue.
Please let me know if you need additional Trajectory IDs, Trace IDs, logs, or diagnostic information.
Thank you.