Intermittent conversation loading failures after new UI update — chats are searchable but randomly fail to open

ChatGPT Bugs
1

After receiving the new ChatGPT web UI, I started experiencing intermittent failures when opening existing conversations.
This initially appeared to affect older normal chats that were no longer visible in Recents. The conversations still appeared in ChatGPT Search, including results matching text inside them, but clicking the search result sometimes produced:
Could not load this ChatGPT conversation

Opening the conversation through its direct /c/<conversation_id> URL did not help.
I then noticed that this is not limited to old or non-Project chats. Some conversations inside Projects also started failing to load intermittently.
The most important behavior is that the failure is inconsistent:

  • A conversation may fail to open once and load normally on the next attempt.
  • A conversation that was loading normally may later produce “Could not load this ChatGPT conversation.”
  • Some chats that previously failed later became accessible again.
  • Both ordinary chats and Project chats can be affected.
  • ChatGPT Search can still find affected conversations and text from inside them even when the conversation itself fails to load.
  • Archived chats currently appear normally for me.
    There also seems to be a related sidebar/Recents issue after the UI update:
  • Some older ordinary chats no longer appear in Recents.
  • They can still be found through Search.
  • Simply opening one does not necessarily restore it to Recents.
  • Editing or regenerating a message in the conversation can cause it to suddenly appear in Recents again.
    Because the same conversation can alternate between loading successfully and failing, this looks like an intermittent conversation-loading or UI synchronization regression rather than permanent deletion of individual chats.
    Reproduction
  1. Use an account that has received the new ChatGPT web UI.
  2. Search for an older conversation using ChatGPT Search.
  3. Open the search result.
  4. The conversation may show “Could not load this ChatGPT conversation.”
  5. Retry later or reopen the same URL.
  6. The same conversation may then load successfully.
  7. Other conversations, including Project chats that previously worked, may fail instead.
    This behavior only started for me after the recent UI update.
    I am reporting this because it makes older conversation history unreliable even though the conversations remain searchable, and there is currently no way to know whether a chat will load successfully on any particular attempt.
2

Same here, however, the chats load on another machine that can control the primary machine.

Using ubuntu24.04LTS

the terminal output looks like this:

[AppServerConnection] response_routed broadcastFallback=false conversationId=null durationMs=9 errorCode=null hadInternalHandler=false hadPending=true method=configRequirements/read originWebcontentsId=1 queueWaitMs=0 requestId=f1df32c0-4b15-445a-baa9-076a96c776c1 targetDestroyed=false
[AppServerConnection] response_routed broadcastFallback=false conversationId=01a0dcb8-16d2-7ec0-8943-1d51b4d16f30 durationMs=1 errorCode=null hadInternalHandler=false hadPending=true method=thread/attachment/list originWebcontentsId=1 queueWaitMs=0 requestId=5a782bbd-7a57-4db6-a04c-3634c82a0729 targetDestroyed=false
[AppServerConnection] response_routed broadcastFallback=false conversationId=null durationMs=2 errorCode=null hadInternalHandler=false hadPending=true method=configRequirements/read originWebcontentsId=1 queueWaitMs=1 requestId=739a8d04-56a3-41a9-aabf-1adbd62e9f37 targetDestroyed=false
[1264012:1264048:0926/182209.891396:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[managed-worktree-archive-queue] Worktree archive will be retried errorMessage="Git is unavailable" errorName=Error errorStack="Error: Git is unavailable\n    at H9.handleWorkerMessage (/usr/lib/chatgpt/resources/app.asar/.vite/build/main-C5425b_s.js:1578:48808)\n    at /usr/lib/chatgpt/resources/app.asar/.vite/build/main-C5425b_s.js:1578:45350\n    at /usr/lib/chatgpt/resources/app.asar/.vite/build/main-C5425b_s.js:1578:42490\n    at Set.forEach (<anonymous>)\n    at Worker.<anonymous> (/usr/lib/chatgpt/resources/app.asar/.vite/build/main-C5425b_s.js:1578:42478)\n    at Worker.emit (node:events:509:28)\n    at MessagePort.<anonymous> (node:internal/worker:350:14)\n    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:856:20)\n    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)" phase=queued