Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix bug: spark usage limited when global usage limited [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
openai/codex#19868•Fetched 2026-04-28 06:35:52
View on GitHub
Comments
3
Participants
3
Timeline
7
Reactions
0
Author
midischwarz12midischwarz12
Participants
github-actions[bot]github-actions[bot]midischwarz12midischwarz12willwang-openaiwillwang-openai
Timeline (top)
commented ×3labeled ×3closed ×1

Error Message

When there is GPT-5.3-Codex-Spark usage left and the Global weekly limit is reached, it is impossible to use GPT-5.3-Codex-Spark with the following error: You've hit your usage limit.

Code Example

│  Context window:              47% left (142K used / 258K)                              │
│  5h limit:                    [████████████████████] 100% left (resets 18:25)          │
│  Weekly limit:                [░░░░░░░░░░░░░░░░░░░░] 0% left (resets 13:43 on 28 Apr)  │
│  GPT-5.3-Codex-Spark limit:                                                            │
│  5h limit:                    [████████████████████] 100% left (resets 19:30)          │
│  Weekly limit:                [████████████████████] 100% left (resets 14:30 on 4 May) │
│  premium limit:                                                                        │
╰────────────────────────────────────────────────────────────────────────────────────────╯
RAW_BUFFERClick to expand / collapse

What issue are you seeing?

When there is GPT-5.3-Codex-Spark usage left and the Global weekly limit is reached, it is impossible to use GPT-5.3-Codex-Spark with the following error: You've hit your usage limit.

From /status:

│  Context window:              47% left (142K used / 258K)                              │
│  5h limit:                    [████████████████████] 100% left (resets 18:25)          │
│  Weekly limit:                [░░░░░░░░░░░░░░░░░░░░] 0% left (resets 13:43 on 28 Apr)  │
│  GPT-5.3-Codex-Spark limit:                                                            │
│  5h limit:                    [████████████████████] 100% left (resets 19:30)          │
│  Weekly limit:                [████████████████████] 100% left (resets 14:30 on 4 May) │
│  premium limit:                                                                        │
╰────────────────────────────────────────────────────────────────────────────────────────╯

What steps can reproduce the bug?

  1. Hit global usage limit
  2. Switch model to GPT-5.3-Codex-Spark
  3. Send prompt

What is the expected behavior?

I should be able to continue using spark still when the general, global weekly usage window is fully consumed.

Additional information

No response

extent analysis

TL;DR

The issue can be worked around by waiting for the global weekly limit to reset or exploring options to increase the usage limit.

Guidance

  • Verify that the global weekly limit is the cause of the issue by checking the /status output for the weekly limit percentage.
  • Check the reset time for the global weekly limit and wait until it resets to try using GPT-5.3-Codex-Spark again.
  • Consider reaching out to support or administrators to inquire about increasing the global weekly usage limit.
  • Review usage patterns to optimize and potentially reduce the likelihood of hitting the global weekly limit in the future.

Notes

The provided information does not specify how to increase the usage limit or if there are any temporary workarounds besides waiting for the limit to reset.

Recommendation

Apply workaround: Wait for the global weekly limit to reset, as there is no clear indication that an upgrade or direct fix is available.

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…
#api#ssr#ISR setup#authentication setup#request error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix bug: spark usage limited when global usage limited [3 comments, 3 participants]