If you are a systems engineer, you know the feeling of a “Silent Failure.” You pay the bill, the invoice says “Active,” and the dashboard shows green—but the API returns a hard 429. For many of us using the Antigravity IDE and Gemini 3.1 Pro, we’ve spent the last 48 hours trapped in a metadata nightmare known as Bug AG-859.
The Technical Breakdown
Google AI Pro is marketed as having a rolling 5-hour refresh window. However, due to a systemic “Metadata Entitlement Sync Failure,” paid accounts are being erroneously bucketed into the Free-Tier “Weekly” lockout.
When we hit a usage limit, the backend ignores our “Pro” flag and enforces a fixed Epoch reset. Instead of waiting 5 hours, we are being told to wait 81 to 160+ hours. This is not a rate limit; it is a Service Denial.
The Audit Trail:
- Error State:
429 MODEL_CAPACITY_EXHAUSTED - The “Smoking Gun”: The
x-goog-ratelimit-resetheader returns a fixed date (currently February 27, 2026) rather than a rolling delta. - Support Failure: Over 125 minutes of live support interaction (Case 8-3336000040583, 0-3873000039771) resulted in “Support Abandonment.” Tier 1 agents admitted they lacked the administrative authority to execute a manual usage bucket flush or a metadata re-sync.
Beyond the Ticket
This isn’t just about a $20 subscription. It’s about the reliability of the developer ecosystem. When a provider accepts recurring payments but lacks the internal triage to fix a documented backend misclassification, the “Pro” label becomes a liability.
I have officially moved this dispute to the regulatory level, filing a formal complaint with the Oregon Department of Justice (Consumer Protection Division) regarding this denial of service and subsequent support abandonment.
If you’re seeing an 81-hour lockout on a paid account, you aren’t crazy, and it isn’t your cache. It’s a server-side logic error that defaults you to a “Free” user the moment you push the model.
#GoogleCloud #GeminiAI #AntigravityIDE #SLA #SystemError #BugAG859