Contact support only after the account-displayed time has passed and a fresh session still shows the old limit.
The decision behind the technique
A public reset post cannot prove what happened to an individual account. Support can investigate incorrect account state, but it is not a shortcut for an ordinary limit that has not reached its displayed recovery time.
Contact support only after the account-displayed time has passed and a fresh session still shows the old limit.
A practical step-by-step workflow
Use this sequence as a default, then tighten or expand it only when the evidence changes.
- Confirm the signed-in account and workspace
- Capture the Usage page, displayed reset time and time zone
- Refresh the session and check the CLI status once
- Send the exact timestamp, screenshots and a minimal reproduction
Failure boundary and finish line
Never include authentication tokens, cookies, recovery codes or local credential files in a support attachment.
Finish when the public claim is labeled separately from the account-level fact and every timestamp includes its time zone.
Frequently asked questions
What should I do first?+
Confirm the signed-in account and workspace
What is the main failure mode?+
Never include authentication tokens, cookies, recovery codes or local credential files in a support attachment.
OFFICIAL SOURCES
Verify against the source
Using Codex with your ChatGPT planThis guide provides general information, not an OpenAI allowance promise or support decision. Your account and official pages govern actual usage, benefits and recovery times.