claude-code - 💡(How to fix) Fix [Bug] Weekly usage limit reset early, losing 36% of quota before scheduled reset time [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52466Fetched 2026-04-24 06:06:28
View on GitHub
Comments
3
Participants
3
Timeline
11
Reactions
1
Timeline (top)
cross-referenced ×5commented ×3labeled ×3

Error Message

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/mandeep/.local/share/claude/versions/2.1.118 (expected in multi-process scenarios)\n at ii$ (/$bunfs/root/src/entrypoints/cli.js:2758:2177)\n at R46 (/$bunfs/root/src/entrypoints/cli.js:2758:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:14:10.457Z"}]

Code Example

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/mandeep/.local/share/claude/versions/2.1.118 (expected in multi-process scenarios)\n    at ii$ (/$bunfs/root/src/entrypoints/cli.js:2758:2177)\n    at R46 (/$bunfs/root/src/entrypoints/cli.js:2758:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:14:10.457Z"}]
RAW_BUFFERClick to expand / collapse
<img width="857" height="532" alt="Image" src="https://github.com/user-attachments/assets/570f24a3-5e2a-4a62-a310-7be65ab21cb8" /> <img width="965" height="667" alt="Image" src="https://github.com/user-attachments/assets/fdcb51b3-2957-4479-8631-583ad7a69953" />

Bug Description Title: [BUG] Weekly usage limit reset ~1h 40min before scheduled reset time — 36% of weekly quota lost

Preflight Checklist

  • I have searched existing issues (related: #49616, #41055, #51222)
  • This is a single bug report
  • I am using the latest version of Claude Code (v2.1.118)

What's Wrong?

My weekly usage limit reset approximately 1 hour 40 minutes before the scheduled reset time shown in /status → Usage. I lost ~36% of my remaining weekly quota across all models as a result.

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

Evidence (two screenshots, same day, same machine):

Screenshot 1 — 9:06 AM PT, April 23, 2026:

  • Current week (all models): 64% used
  • Resets: 12pm (America/Los_Angeles)
  • Current session: 5% used

Screenshot 2 — 10:21 AM PT, April 23, 2026 (~1h 40min before scheduled 12pm reset):

  • Current week (all models): 0% used (bar empty)
  • Resets: Apr 28, 1:59pm (America/Los_Angeles) — a brand-new 7-day window had already started
  • Current week (Sonnet only): 0% used
  • Current session: 10% used, resets 2:59pm

The new reset date of April 28, 1:59pm implies the new week began at approximately 1:59pm PT on April 21 (7 days earlier) — but the reset fired and the counter zeroed out at approximately 10:21 AM PT on April 23, while I was still entitled to my remaining 36% of the previous week.

Expected behavior:

The weekly usage limit should reset exactly at the displayed reset time (12pm PT on April 23), not earlier. Remaining quota in the current week should remain available until the actual scheduled reset.

Actual behavior:

The reset fired at approximately 10:21 AM PT, roughly 1 hour 40 minutes early. Remaining 36% of weekly quota was wiped without being usable.

Environment:

  • Claude Code version: 2.1.118
  • Model: Opus 4.7 (1M context)
  • Plan: Claude Max
  • OS: Ubuntu Linux
  • Platform: CLI (terminal)
  • Timezone: America/Los_Angeles

Impact:

~36% of weekly quota across all models lost. Requesting quota credit for the lost allocation and an engineering fix so this does not recur.

Related issues (this is a recurring pattern):

  • #49616 (weekly limit reset 4+ hours early, April 17, 2026)
  • #41055 (weekly reset failures on Max plan)
  • #51222 (reset time display inconsistencies)

I have both screenshots available and will attach them to this issue. Both images are ~/Downloads/bugs

Environment Info

  • Platform: linux
  • Terminal: gnome-terminal
  • Version: 2.1.118
  • Feedback ID: 480cf030-26d1-41dd-ad72-6293c1a38d0f

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/mandeep/.local/share/claude/versions/2.1.118 (expected in multi-process scenarios)\n    at ii$ (/$bunfs/root/src/entrypoints/cli.js:2758:2177)\n    at R46 (/$bunfs/root/src/entrypoints/cli.js:2758:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T17:14:10.457Z"}]

extent analysis

TL;DR

The weekly usage limit reset approximately 1 hour 40 minutes before the scheduled reset time, resulting in a loss of 36% of the weekly quota, and a potential fix may involve adjusting the reset timing mechanism.

Guidance

  • Review the reset timing mechanism to ensure it aligns with the displayed reset time, considering potential timezone or clock skew issues.
  • Investigate the Lock acquisition failed error to determine if it's related to the premature reset, as it may indicate a concurrency or synchronization issue.
  • Compare the system clock and timezone settings with the scheduled reset time to identify any discrepancies.
  • Consider implementing a buffer or tolerance in the reset timing to account for minor clock variations.

Example

No code example is provided due to the lack of specific implementation details, but the investigation should focus on the timing and synchronization aspects of the reset mechanism.

Notes

The issue may be related to a recurring pattern, as mentioned in the related issues (#49616, #41055, #51222), and addressing the root cause will likely require a thorough review of the reset timing and synchronization mechanisms.

Recommendation

Apply a workaround by closely monitoring the reset times and quotas to minimize losses until a permanent fix is implemented, as the exact cause and solution are still uncertain.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING