Weekly usage allowance does not reset after subscription renewal: intended behavior or oversight?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
After renewing my ChatGPT subscription, my Codex weekly usage allowance did not reset.
I find this confusing: I have paid for a new subscription period, but the weekly allowance has not been replenished. Is this intended behavior, or could it be an oversight in how subscription renewals are handled?
What steps can reproduce the bug?
The sequence I observed was:
- Renew the subscription.
- Check the Codex weekly usage allowance after renewal.
- Observe that the weekly allowance has not reset.
What is the expected behavior?
I expected the weekly allowance to refresh when the new paid subscription period began, but I am unsure whether weekly usage windows are intentionally independent of billing cycles.
Could you please clarify:
- Should subscription renewal reset the weekly Codex usage allowance?
- If not, what determines the weekly reset time?
- If this is intentional, could the usage page or renewal flow explain it more clearly?
If renewal is supposed to reset the allowance, please investigate why that did not happen.
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no repository file, test, or code entry point. Start by confirming whether the weekly allowance and subscription renewal use separate reset rules, then trace the renewal and allowance behavior; done means the intended reset policy is established and the observed behavior is either corrected or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100