[BUG] Weekly usage limit reset 4+ hours before scheduled reset time

Status Closed — not planned
Maintainer reply None cached
Activity 14 comments · opened Apr 17, 2026 · closed Jul 26, 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?

My weekly usage limit reset approximately 4+ hours before the scheduled reset time shown in Settings → Usage. I lost 20%+ of my remaining weekly quota as a result.

What Should Happen?

The weekly limit should reset at the scheduled time shown in Settings → Usage, not before.

Error Messages/Logs

Error Messages/Logs
None visible in the app.

Steps to Reproduce

This occurred automatically without any user action.

  1. Check Settings → Usage — reset time was shown as later today.
  2. Approximately 4+ hours before that scheduled time, the reset occurred unexpectedly.
  3. Remaining quota (20%+) was lost.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

Claude Code Version 1.3109.0 (35cbf6) 2026-04-16T20:32:01.000Z

Claude Code Version

Claude Code Version 1.3109.0 (35cbf6) 2026-04-16T20:32:01.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Additional Information
Noticed at approximately 8:20 AM KST, April 17, 2026.
Contacted Fin AI support but they were unable to investigate account logs or submit bug reports on behalf of users.

View original on GitHub ↗

13 Comments

github-actions[bot] · 4 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/49599
  2. https://github.com/anthropics/claude-code/issues/49567
  3. https://github.com/anthropics/claude-code/issues/29680

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

williambe · 4 months ago

Same issue here, reporting independently.

Plan: Claude Max 5x
Claude Code version: 2.1.112
macOS 15.7.4
Timezone: CET (UTC+2, Europe/Rome)
Date: Friday, April 17, 2026

For the entire week, Settings → Usage displayed a reset time of approximately 17:00–19:00 CET on Friday. This morning the reset occurred at approximately 06:00 CET — 11 to 13 hours earlier than shown.

Approximately 35% of remaining weekly quota was lost as a result.

Usage pattern: Claude Code for knowledge management and structured document work. I do run parallel sessions and some have background jobs enabled via Claude Code. However, this does not explain the discrepancy: the issue is not quota consumption rate, but the fact that the reset occurred 11-13 hours before the time explicitly shown in the UI. The displayed reset time was stable and consistent throughout the entire week, then the actual reset happened hours earlier without any change reflected in the interface.

I reported this to consumer support via chat. Their response acknowledged it as a UI accuracy issue ("this does sound like a UI accuracy issue rather than a misunderstanding of the rolling reset system") but confirmed they cannot escalate, restore quota, or acknowledge specific GitHub issues. They directed me to use /bug in Claude Code, which I have also done.

Update – April 24, 2026

The bug occurred again. Reset happened at 23:43 CET on Thursday April 24, approximately 6 hours before the scheduled Friday 06:00 CET.

This created two completely opposite scenarios with no way to know which was real:

Scenario A – next reset April 25 (36-hour cycle): an unplanned short cycle, a net gain in usable quota.

Scenario B – next reset May 2 (8.5-day cycle): an abnormally long window requiring significant reduction in daily usage to avoid hitting limits or incurring extra costs.

Running /usage in Claude Code confirmed Scenario A: "Resets Apr 25 at 12pm (Europe/Rome)". This instance is a net gain for the user.

However, the bug is not always favorable. Depending on where the system re-anchors after each early reset. The unpredictability makes it impossible to plan usage reliably.

phoradan · 4 months ago

Everyone : Please THUMBS DOWN the auto-duplicate comment above so this does not get auto-closed as a duplicate. I don't believe this is a duplicate of any linked issue. I can't find a dup issue that matches my experience.

This has happened to me several times. I keep Claude -> Settings -> Usage window open all week. My reset time used to be Friday at 11am. Then it became Friday at 2am. Then just this week, it moved back to Thursday at noon.

Each time the limit moves ahead in the week. Each time I lose my unused usage - often 20% of quota. I can't find any reason for it. Claude itself can't explain it.

REPRO:

  • Monitor weekly Opus 4.6 reset date/time via Claude -> Settings -> Usage
  • As that reset date/time approaches, about 1/3 of the time, the reset date will move ahead in time

IMPACT:

  • Usage quota is lost and couldn't be used before the deadline

EXPECT:

  • Weekly Opus 4.6 reset date to stay consistent, or at least have a deterministic/transparent change process
saravananthangaraju78-prog · 4 months ago

The Plan was supposed to reset on Friday (today) at ~4:00 pm. I usually use 15% everyday. On Thursday 5 pm, looks like it reset and now the usage shows the reset happens on Thursday 4:59 pm. Lost over 15% and lost 15% of the current usage. I am thinking it is still working with the last week's usage and draining it down.

ryonagamine-oss · 4 months ago

My weekly usage limit was supposed to reset today (Saturday) at 7 PM, but it had already reset at friday morning at 5 AM — more than a day early. Why did this happen? And what happened to the roughly 30% of my weekly quota that I should have been able to use until this morning? Is it just gone?I want it back!

kibongkook · 4 months ago

My weekly reset day has shifted from Wednesday to Friday with no explanation, even though I use Claude every single day without interruption. Under the documented rolling 7-day logic, daily usage should anchor the reset window — it should not drift 2 days backward.

iliatoli · 4 months ago

Adding a much more severe instance of this same bug. My weekly reset fired
approximately 2 days early, not hours early — and the displayed reset
time shifted backward in stages before the early reset occurred, which
I haven't seen documented yet in this thread.

Timeline (America/Chicago, CDT), Pro plan:

  • Initial state: Settings → Usage displayed weekly reset at Friday, 4:00 PM.
  • Later: Displayed reset had moved to Thursday, 4:00 PM (−24h).
  • Later: Displayed reset had moved to Wednesday, 9:00 PM (−19h further;

−43h total vs. original).

  • Shortly after: weekly counter actually reset at approximately Wednesday 9 PM.

Net forfeiture: roughly 2 days of the previous week's allocation
(Wednesday-evening through Friday-afternoon).

Notable detail: the displayed reset time shifted backward monotonically
across multiple observations before the actual reset fired. This is the
inverse of the forward-shift documented in #51222, but produces the same
harm. Together, #49616 (4h early), this case (~2d early), #51222
(postponed forward), #30933 (displayed time passes without reset), and
#41055 (reset fails entirely on Max) suggest the weekly-window anchor
logic has multiple uncorrelated failure modes.

Requesting Anthropic publish the anchor-update rules so users can
reconcile displayed reset times with actual reset behavior. The current
opacity makes it impossible to distinguish bug from silent policy from
billing-relevant error.

Filed separately as #52498 before finding this thread; closing that in
favor of this one.

kaushiksa · 4 months ago

Facing the same issue, reset happened 12h earlier + different stats for weekly usage on my vs's claude code extension and web interface (reset schedule)

<img width="473" height="511" alt="Image" src="https://github.com/user-attachments/assets/a387dc00-2bb4-4010-82d8-69d19fa1b817" />
<img width="1366" height="685" alt="Image" src="https://github.com/user-attachments/assets/1162e980-61c5-4b2b-9db3-961682038b84" />

LeamHall · 4 months ago

Same issue here, reset 4 hours early and I lost over 60% of my weekly usage. The filenames have the timestamps, if they don't show it was at 1424 (2:45 PM) and the original reset time wasn't until 1800 (6 PM).

<img width="1467" height="959" alt="Image" src="https://github.com/user-attachments/assets/a1aa7fc7-2401-4a4e-a4a6-d387e6c4f869" />
<img width="1467" height="959" alt="Image" src="https://github.com/user-attachments/assets/3c25b75b-a8a5-4672-86a7-1dca34f3b056" />

gprepok · 4 months ago

Same issue. I am usually checking the usage on the website Settings->Usage:
Previous session was to reset at 2026-04-23T08:00:00Z when time passed the UI changed to 2026-06-24T00:00:00Z. this was annoying but not super worrying.
But now I started a new 7 days (weekly) session around 2026-04-24T08:00:00Z but the UI says it will reset tomorrow 2026-04-25T13:00:00.902365+00:00

<img width="1555" height="684" alt="Image" src="https://github.com/user-attachments/assets/8064e611-fe58-4324-8cb4-a313d3aa5059" />

marcindulak · 3 months ago

A reset of weekly limits about 21 hours too early also happened to me on 2026-05-15, on the Pro plan.
I still had usage left in the current weekly limit.
After the reset the reset time had not changed - it still had 21 hours left until the next weekly reset.

<img width="1498" height="912" alt="Image" src="https://github.com/user-attachments/assets/7f6415e6-50aa-4dab-878f-a28ddc3543e8" />

marcindulak · 2 months ago

An early reset of weekly limit may be happening around certain events at Anthropic, like release of new models.

A reset happened to me also on:

Thursday May 28, 2026 https://www.anthropic.com/news/claude-opus-4-8
Friday Jun 12, 2026 https://www.anthropic.com/news/fable-mythos-access

However, the reset on Friday May 15, 2026 does not correspond to any announcement https://www.anthropic.com/news or model retirement https://platform.claude.com/docs/en/about-claude/model-deprecations#model-status.

github-actions[bot] · 1 month ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

Showing cached comments. Read the full discussion on GitHub ↗