You just got a fresh weekly quota on Claude. Zero percent used. But you still can't send a message because your session limit is maxed out from the previous burst - and it won't reset for another four hours.
That's the situation Claude Pro subscribers are running into. The platform enforces two separate rate limits: a weekly usage cap and a shorter session-based cap designed to prevent burst overload on the servers. The problem is these two systems don't talk to each other. When your weekly quota resets, the session limit keeps its own countdown. So you can stare at a dashboard showing 0% weekly usage while being completely locked out.
Anthropic hasn't publicly addressed the interaction between these two limits. The session cap makes sense as infrastructure protection - you don't want one user hammering the API nonstop - but the current behavior creates a confusing experience. Users reasonably expect a weekly reset to mean they can, you know, use the product. A simple fix would be to clear the session counter whenever the weekly quota refreshes, or at minimum, show both timers clearly so users can plan around them.
For now, the workaround is simple if annoying: don't burn through heavy usage right before your weekly reset. Space it out, or accept the dead zone. It's a small UX gap, not a dealbreaker, but it's the kind of rough edge that $20/month subscribers notice.