[BUG] Weekly usage limit not updated after upgrade from Pro to Max 20x — account still behaves as Pro/5x

Resolved 💬 1 comment Opened May 11, 2026 by brunojukinha Closed Jun 16, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

On May 5th, 2026, I upgraded my Claude.ai subscription from Pro to Max 20x. The session limit (5-hour window) updated correctly and reflects the new plan, but the weekly usage limit did not update — it still behaves as if I am on the Pro/5x plan.

Concrete evidence:

  • Last week: I hit 100% of the weekly cap on "all models" before the middle of the week, exactly as I used to on Pro.
  • This week: the weekly limit reset on Sunday at 06:00. It is now Monday (one day into the new cycle) and I have already consumed ~30% of the weekly cap. At this pace I will hit 100% again mid-week.
  • The Max 20x plan advertises 20x the session capacity of Pro plus proportionally higher weekly caps. My account is clearly not receiving that.

I have already opened a support ticket on May 8th (Conversation ID 215474226838507). The Fin AI agent acknowledged that this looks like a technical issue with how the Pro → Max 20x upgrade was processed and said it would require human investigation. I formally requested escalation to a human specialist and have received no human response in 3 days.

I am opening this issue because:

  1. The bug is observable in the account behavior, not just a billing question.
  2. Claude Code authenticated with the Max plan shares the same weekly quota, so the bug also impacts Claude Code usage.
  3. Support has not responded.

What Should Happen?

The weekly usage limits on my account should reflect the Max 20x plan I paid for on May 5th, 2026. Specifically:

  • The "All models" weekly cap should be substantially higher than the Pro plan cap.
  • The "Sonnet only" weekly cap should also reflect Max 20x levels.
  • At normal professional usage (no session hitting 100%), I should not exhaust the weekly cap mid-week.

Expected outcome: backend review of the upgrade process, correction of the weekly limit values associated with my account, and confirmation that the fix is applied.

Error Messages/Logs

When the weekly cap is reached, Claude.ai displays a message stating that the weekly usage limit has been reached and shows a reset date (next Sunday at 06:00). No technical stack trace — this is a quota enforcement message, not a software crash.

Steps to Reproduce

This bug requires access to my specific account and is not externally reproducible. Internal reproduction steps would be:

  1. Identify the account associated with bruno.porreca@soulivon.com.br
  2. Verify the upgrade event from Pro to Max 20x on May 5th, 2026
  3. Compare the weekly usage limit values currently assigned to this account vs. the documented Max 20x values
  4. Observed: weekly limits appear consistent with the Pro plan, not Max 20x
  5. Expected: weekly limits should match Max 20x specification

Support Conversation ID for cross-reference: 215474226838507

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.118 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

  • Support ticket opened: May 8th, 2026
  • Conversation ID: 215474226838507
  • Channel: support@mail.anthropic.com (Fin AI Agent)
  • Status: no human response received in 3 days
  • Account email: bruno.porreca@soulivon.com.br
  • Plan: Max 20x (since May 5th, 2026)
  • Impact: this directly affects my professional work, as I depend on Claude daily.

Screenshots of Settings > Usage attached, showing the consumption pattern inconsistent with the Max 20x plan.

<img width="1511" height="908" alt="Image" src="https://github.com/user-attachments/assets/e8cddfbb-7876-4970-929d-66ef33747026" />

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗