I have already waited for 77 hours, and now I am going to conduct an experiment. Once the quota is restored, I will use 80% of it, leave 20% remaining, and wait for 5 hours. If the quota is not restored at that point, it proves that the visible quota bar does not represent a 5-hour refresh cycle, but rather only half of a weekly allowance."
"If the wait time jumps to 77 hours again, it confirms that a 77-hour lockout occurs twice a week, meaning the actual weekly quota is only about two full bars of what is displayed. I will compare this directly with a Free model. Currently, I believe this is either a bug or a fundamental issue with Googleâs system. Furthermore, Google stated in their latest update that they fixed a bug causing excessive quota consumption; they have already acknowledged that quota-related bugs exist. The bugs clearly exist.
Hello,
Thank you for bringing these concerns to our attention. Please be assured that I have shared your feedback with our internal team for further review. You can follow the updates in the main thread.
That the âmain threadâ has no updates since it was started in late January makes it quite clear your âinternal teamâ either isnât getting the message, or is ignoring it.
P.S. I observed two critical anomalies during my test:
1. Quota Bar UI Glitch (Stuck at 100%)
Based on my typical usage, the quota bar should have dropped to at least 40-60%. However, it remained frozen at 100%. This proves a severe discrepancy between the displayed UI and the actual server-side restriction. Please refer to my attached screenshot for evidence.
2. Introduction of the âCreditsâ System
When I clicked the refresh button, a new âCreditsâ feature appeared. I was given 1,000 default credits, along with a prompt suggesting that more credits must be purchased for continued use. It is unclear whether these credits are granted weekly, monthly, or only once. This hidden credit system seems to be overriding the promised 5-hour refresh for Pro users.
1 Like
