Urgent: Erroneous 167-hour Lockout on Antigravity IDE (Bug Report)

Google Antigravity
1

Description: I am writing to report a critical issue where my account has been incorrectly flagged with a 7-day (167-hour) usage cooldown in the Antigravity IDE. I am currently working on a time-sensitive development project for an AI-based emotional support application utilizing Gemma 3. This lockout is currently preventing me from continuing development on this project.

I believe this is an entitlement synchronization bug, as I am not attempting to circumvent any rate limits and this appears to be an erroneous “Baseline” lockout.

Technical Details:

  • Error ID: 7989e04fd4bd4549bec247733ad524..

  • Trajectory ID: 88f03696-6d40-4810-9038-26805fe1f5..

Request: Could a member of the support or engineering team please review these IDs and perform a manual metadata sync or entitlement reset on my account? Access to the IDE is vital for my project’s progress.

Thank you for your assistance.

2

Hello @Shayan_Sheikh.

The 167-hour lockout is intended system behavior rather than a bug. The system operates on a dual-limit structure: a 5-hour refresh for ongoing usage and a larger weekly quota. Once the total weekly premium quota is exhausted, the system transitions to a multi-day cooldown until the next weekly cycle.

  • Standard Refresh: The 5-hour refresh is primarily designed to manage regular, ongoing usage throughout the week.
  • Weekly Reset: Once your full weekly premium quota is completely exhausted, the system transitions into a much longer cooldown period until your next weekly cycle resets.

To better track your usage, can you ensure your Antigravity client is updated to the latest stable release, version 2.1.1? This version includes a redesigned Quota screen under Settings > Models that provides a clear view of your remaining weekly limits to help pace your token usage.