Banked Codex resets disappeared after a brief subscription lapse and immediate Pro reactivation

What issue are you seeing?

I had four banked Codex rate-limit resets that were already granted and visible in the Usage interface. I briefly allowed my ChatGPT Pro subscription to lapse while replacing an expired payment card, then immediately restored the same plan once the replacement card arrived.

After reactivation, all four banked resets disappeared. I did not redeem any of them.

This is distinct from a reset merely failing to appear after a campaign announcement: these resets had already been visible and available. Support confirmed that my Pro entitlement was active after reactivation, but the follow-up did not identify an account-specific event or rule explaining why the existing resets were removed.

What steps can reproduce the bug?

This may be account- and time-dependent, so I cannot reproduce it on demand. The observed sequence was:

1. Have banked Codex resets visible in the Usage interface.
2. Allow a paid ChatGPT subscription to lapse briefly while changing payment method.
3. Restore the same paid plan immediately.
4. Reopen Codex Usage.
5. Observe that previously visible, unused banked resets are no longer available.

I did not select or apply any reset during this sequence.

What is the expected behavior?

Previously granted banked resets should remain visible and usable until their disclosed expiration, unless a clearly communicated offer term or account-status rule authorizes removal. If a reset is removed, the Usage interface should show the reason and relevant event details.

Additional information

Requested investigation:

• Check the server-side entitlement and reset ledger for each of the four resets.
• Confirm whether each reset was redeemed, expired, revoked, or otherwise removed.
• Identify the exact timestamp, applicable time zone, and policy or offer term for each event.
• Confirm whether a temporary subscription lapse can cancel already-granted resets and, if so, where that consequence is disclosed.

Related public reports describe banked resets disappearing, being consumed without restoring usage, or lacking a clear event history. Those reports may not have the same cause, but they support a broader need for a user-visible reset ledger.

If you have a matching experience, please react.

No repository file or test is named. Start by reviewing the server-side entitlement and reset ledger for the four resets, then trace the subscription lapse and reactivation events. Done means identifying whether each reset was redeemed, expired, revoked, or otherwise removed, including timestamps, policy terms, and any user-visible explanation.