[BUG] Google AI Pro — Gemini 3.1 Pro (High & Low) 5-Day Lockout, 5-Hour Reset Not Honored
Plan: Google AI Pro (active, paid subscription)
Antigravity Version: 1.20.4
OS: macOS ARM64 (Apple Silicon)
Date issue started: March 8, 2026
Problem Description:
I am an active Google AI Pro subscriber experiencing a 5-day quota lockout specifically on Gemini 3.1 Pro (High) and Gemini 3.1 Pro (Low). Both models show “Refreshes in 5 days, 0 hours” — directly contradicting the advertised 5-hour refresh cycle for Pro subscribers.
Current quota status (verified in Settings → Models):
• Gemini 3.1 Pro (High): LOCKED — Refreshes in 5 days, 0 hours ![]()
• Gemini 3.1 Pro (Low): LOCKED — Refreshes in 5 days, 0 hours ![]()
• Gemini 3 Flash: Working — Refreshes in ~4 hours ![]()
• Claude Sonnet 4.6 (Thinking): Working — Refreshes in ~4 hours ![]()
• Claude Opus 4.6 (Thinking): Working — Refreshes in ~4 hours ![]()
• GPT-OSS 120B: Working — Refreshes in ~4 hours ![]()
The lockout appears isolated to Gemini 3.1 Pro models only. All other models are functioning with correct ~5-hour refresh cycles.
Exact error seen in chat (previous session):
“You have exhausted your capacity on this model. Your quota will reset after 2h4m37s.”
“Your plan’s baseline quota will refresh on 08/03/2026, 13:20:47.”
After baseline refresh the models did NOT restore the 5-hour cycle — instead both Gemini 3.1 Pro models are now showing a 5-day lockout.
Steps to Reproduce:
- Use Gemini 3.1 Pro (High or Low) in Planning mode on a complex multi-file task
- Hit the rolling quota limit
- Wait for the stated reset time
- Observe that instead of a 5-hour rolling reset, both Gemini 3.1 Pro models now show a 5-day baseline lockout
Requested Actions:
- Manual quota reset for Gemini 3.1 Pro (High) and Gemini 3.1 Pro (Low) on my account
- Confirmation of whether the 5-hour refresh cycle applies to Gemini 3.1 Pro for Pro subscribers
- Clarification on what triggers the “baseline quota” vs the rolling 5-hour quota
I have seen multiple threads reporting this same pattern:
Threads #114724, #118505, #122780, #124839, #127183, #127678, #127825
This appears to be a widespread and ongoing bug specifically affecting Gemini 3.1 Pro models after the Gemini 3.1 rollout (February 19-20, 2026).
Thank you.

