#🚨Disappearing Messages in Specific Chats 🚨

1 messages ¡ Page 1 of 1 (latest)

gritty sonnetBOT
#

Reported by @regal vault

Bug Report: 🚨Disappearing Messages in Specific Chats 🚨
`Steps to Reproduce`

  1. Open a chat in chat GPT that had previously hit the conversation length limit before the limit was removed.

  2. Try to use the chat normally.

  3. Leave and re-enter the chat.

`Expected Result`

It should've work like it never hit that limit since it was removed (conversation length limit I mean)

`Actual Result`

It still shows the message of conversation length limit which was removed, voice feature doesn't work but with leaving and re-entering that chat it will be gone (the conversation length limit message) but in worse cases the chat would be refreshed and the reply would be gone and says something went wrong and then it answers again and shows the removed length limit's message but you can still message yourself since the limit itself doesn't exist

`Environment`

All platforms

#
Additional Information

Please provide relevant details to help resolve the issue, such as:

  • ChatGPT Shared Link (if applicable).
  • Screenshots or videos demonstrating the problem.

-# ➜ Need to contact support? Visit the OpenAI Help Center.

regal vault
#

Just adding some extra context in case it helps: the issue doesn’t affect all chats, only ones that previously hit the old conversation length limit before it was removed. New chats work fine. So it seems tied to how older chats are stored rather than the current system.

regal vault
#

We need to get it fixed

regal vault
#

This isn’t a normal bug — it’s a leftover regression from when the conversation length limit was removed. Chats that hit the old limit still behave differently (messages vanish, voice disabled, UI refresh wipes answers). That means the removal wasn’t fully cleaned up in backend. It’s not an isolated glitch, it’s leftover system state, Issue is present on all platforms (web, iOS, Android, desktop). I tested VPNs, networks, reinstall — doesn’t matter. That rules out client/device issues and points 100% to server/backend state tied to specific conversations, This doesn’t require a new feature — just cleanup of old conversation state from before the limit removal. A migration script or refresh could likely fix it in one sweep. Right now those old chats are basically ‘corrupted’ and can’t function normally

regal vault
#

Update on the bug:
I tested again and confirmed it’s not DNS or device related. In my worst affected chat, forcing a regeneration on the stuck “nothing” reply temporarily fixed it — the chat behaved normally until I closed and reopened the app, then it went back to being broken.

This shows it’s a UI/backend mismatch bug: the length-limit banner logic is still messing with voice + replies even though the limit was removed. It’s not a connection issue.

ripe root
#

hi

regal vault
#

Hi

livid cobalt
#

Suggenstion: using a browser add on save all the chat in a txt filr.
then, delete 2/3 of the chat and put on the txt file to preserve the content. Move forward from there. You reset the cache size and you can keep doing so if you like the way the runtime cached after the 1st input- prolly an old chat less leashed

dense leaf
#

Can u provide Chat GPT API

#

Free Version

regal vault
# livid cobalt Suggenstion: using a browser add on save all the chat in a txt filr. then, delet...

Well the problem isn't something to be solved in our side because after the limit was removed the chats that already hit it were stuck with a glich which was like half limited the chat can still be continued as of the last improvement I've seen but the voice gives the error "something went wrong" and the limit message still exists in the UI but does nothing since you can reply even while the limit message is there

regal vault
regal vault
#

This bug/glitch hasn't been completely fixed but has become better and less glichy

unborn yoke
#

i have steps to fix i think