/usage-credits blocked after quota reset: stale request state persists across periods
Resolved 💬 1 comment Opened Jun 4, 2026 by maximchouinard Closed Jul 10, 2026
Description
After a quota period resets, the /usage-credits command still returns:
You've already sent a usage credit request to your admin.
This prevents users from requesting additional credits in the new period, even though the previous request was from a prior quota cycle.
Steps to Reproduce
- Send a
/usage-creditsrequest near the end of a quota period. - Wait for the quota to reset (new period begins).
- Use up credits in the new period.
- Run
/usage-creditsagain — command is blocked with the stale message above.
Expected Behavior
The "already sent" state should be cleared when the quota period resets, allowing users to send a new request in the new period.
Actual Behavior
The command remains blocked indefinitely, forcing users to contact their admin out-of-band.
Environment
- Claude Code CLI
- Enterprise/team account
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗