[CRITICAL BUG] Quota Reset Failure: Timers jumping from "0 hours" to "6 days" without usage (Pro Plan)

Hi Google AI Team / Antigravity Support,

I am reporting a reproducible bug where the Pro-tier 5-hour refresh cycle is failing to reset and is instead triggering a multi-day lockout, despite zero usage during the transition period.

The Bug: The “Post-Refresh” Lockout

This is not a case of hitting a limit through usage. I have observed the following behavior twice now:

  1. The Countdown: My Gemini 3.1 Pro quota showed a refresh time of ~3 hours remaining.

  2. The Idle Period: I did not use the IDE or any AI models during these 3 hours. I waited for the refresh.

  3. The Flip: Once the timer hit zero, instead of my quota bars filling back up, the UI immediately updated to show a refresh in 2 days, 2 hours.

  4. Global Contagion: Simultaneously, other models (Claude 4.6, GPT-OSS) that were also nearing refresh jumped to a 6 day, 13 hour cooldown.

Technical Analysis

This suggests a logic error in the Quota Reconciliation Service. It appears that upon the expiration of a short-term (5-hour) window, the system is incorrectly defaulting Pro accounts into the “Free/Weekly” bucket rather than renewing the “Pro/Rolling” bucket.

This is a critical failure of the Pro subscription value: * I am being locked out of the service because the timer expired, not because I used the service.

  • The system is penalizing idle Pro accounts with 150+ hour wait times.

Evidence

(Attached Screenshot: image_86655b.jpg) My screenshot shows desynchronized timers where Gemini 3 Flash is on a 5-hour cycle, while every other premium model—which should refresh on the same Pro cadence—has been pushed into a multi-day “ghost” cooldown.

Request

  • Investigate the transition logic: Why does a timer reaching 0:00 trigger a multi-day lockout instead of a refill for Pro users?

  • Manual Reset: Please reset the quota_epoch for my account so I can resume work.

  • Acknowledge the “Weekly Cap” Bug: Is there a secondary weekly cap that is being triggered prematurely or incorrectly by the 5-hour refresh service?

2 Likes