Regression: Long conversations that previously loaded are now completely inaccessible for many users

Starting a few days ago, multiple long conversations that I’ve accessed regularly for over a year are now failing to load. Looking for engineering visibility on this. This bug has affects Android, Windows, and web so its not platform-specific. Shorter old conversations load fine. Only max-length conversations are broken. Multiple users on Reddit reporting identical issue starting same timeframe. These chats loaded fine for 12+ months until this week. I have tried different devices, different browsers, incognito mode, clearing cache. None worked as expected, since this is clearly server-side.

Contacted support with error IDs, screenshots, pattern identification, and links to other affected users. Response was standard troubleshooting (clear cache, try different browser). Also told “we’re not able to directly escalate tickets from this channel.”

Is engineering aware of this regression? Something changed backend-side that broke retrieval for long conversations. The data exists so export should still work. But the UI can no longer serve these chats.

Any visibility appreciated. Happy to provide error IDs or additional details.

1 Like

Hey @Athelaperk, yeah, that’s a pretty rough experience, especially if those conversations were showing before.

Can you share your support case ID? That’ll help us look up what’s already been investigated and see what’s going on behind the scenes.

If you have any patterns too like when it started or if it’s tied to longer threads specifically, that can help connect the dots.

-Mark G.

1 Like

Same here. The old chats that were maxed out no longer open. It mostly affects chats that used the 4o version. I first noticed the issue on April 7. Support keeps telling me it’s an isolated case, but it’s very obvious that it isn’t.

A lot of my old conversation fail to load as well- most of them using 4o…-_-