xAI Reset Grok Build Limits Due to Caching Issues

xAI Resets Grok Build Limits Due to Caching Issues

xAI announced a reset of usage limits for Grok Build Beta across all accounts. The issue was caused by caching system problems that led users to hit restrictions too quickly.

The limits problem

After launching Grok Build Beta, many users faced an unexpected problem: they hit usage limits very quickly. Users noted that after just a few attempts to use the tool, they received a message about exhausted limits. This was especially frustrating for testers who wanted to understand what the new tool could do, but couldn't fully explore it due to restrictions.

This prevented proper feature testing, feedback collection, and understanding of Grok Build's real capabilities. xAI actively collected complaints and feedback from users on social media, Reddit, and other channels, understanding that the problem was widespread among testers and required urgent attention. For developers, it's very important to understand what exactly is hindering users, and xAI did not ignore the criticism.

Technical reason

The xAI engineering team conducted a detailed analysis of the logging system and identified the root cause of the problem — failures in the caching system. The cache incorrectly accounted for used resources, which led to premature triggering of restrictions. The system mistakenly believed that the user had already exhausted their limits, when in fact they had used only a small portion of their allocated request budget.

After discovering the problem, the team focused on optimizing caching to ensure the system properly tracked actual resource usage. Significant work was done to rework the cache logic, new verification mechanisms were added, and fixes were tested on various usage scenarios. xAI engineers also checked whether this problem was repeating elsewhere in the system.

Solution and limits reset

After fixing the issue, xAI decided to reset usage limits for all accounts, giving users a second chance to properly test the tool. Along with this, all fixes were implemented in the caching system and testing was conducted across all platforms:

• Complete reset of usage counters for all users
• Fixed caching system that more accurately counts resources
• Restoration of the ability to fully test Grok Build Beta
• Resumption of feedback collection from the community

The company expressed gratitude to users for sharing the problem and helping to identify a critical bug, and actively asks users to continue sending feedback and suggestions for improving the tool. This helps xAI make the final version of Grok Build truly useful and reliable.

What this means

This demonstrates xAI's correct and user-oriented approach to developing and testing new features. The beta phase involves exactly this cycle: fast feature release, active feedback collection, problem detection, fixing them, and a new round of testing. xAI did not hide the problem, did not ignore complaints, but responded promptly to criticism and worked on a solution. This increases trust in the team and gives hope for high quality of the final product.