Error messages

Unable to load conversation

Unable to load conversation

You click a chat in the sidebar and get a red banner instead of your messages, usually with the chat's ID on the end:

Unable to load conversation 67a21831-4e54-8000-bf0f-de8a1260a96e

The ID is the chat's own (chat links look like chatgpt.com/c/<id>). Since the web redesign in late September 2026 the same failure often reads "Could not load this ChatGPT conversation" instead. OpenAI's troubleshooting page for ChatGPT errors doesn't list either wording as of October 1, 2026.

What OpenAI Support has said about it

An OpenAI_Support account answered a thread in April 2026 with the closest thing to an official reading: "Issues like this can sometimes happen for a few different reasons - for example, longer or more complex conversations, or temporary loading issues." When the same person said it hit every chat on web and Android for a week, Support said that "does point more toward something account-specific" and moved it to a ticket.

Two problems OpenAI has acknowledged sit behind recent waves of this error.

• Long chats (April to September 2026). From about April 7, chats that had hit maximum length stopped opening on web, Android and Windows while shorter ones were fine. On September 16 OpenAI Support posted that "the issue affecting access to older or longer conversations has since been fixed". One user said the next day it still wasn't fixed for them.
• Rate limiting after the redesign (late September 2026). People saw 429 "Too many requests" responses in their browser's network log while chats refused to load. On September 29 Support said engineering had "rolled out an improvement that stops Chat and Work from unnecessarily refreshing history after every completed turn" to cut the repeated requests. Some reported it fixed straight away. Others on October 1 still had one chat that wouldn't open.

What's worked for people

On the September 2026 rate-limit problem, two people found the same thing: close every ChatGPT session (browser tabs, the desktop app, the phone app, Codex) and leave it for about half an hour before reopening. One of them said the limit seems to reset after that long.

From the older forum thread, which has close to 200,000 views, two tricks came up more than once. Requesting a data export (Settings, then Data Controls) made stuck chats load again for some users, though one said it came back later. In early 2024 several people fixed it by switching the language setting off the "Alpha" locale option back to automatic or English. A moderator also pointed out once that it lined up with a live outage, so check status.openai.com before anything else.

If the banner adds conversation_tree_inconsistent, you're in thinner territory. The one person who posted it, in 2025, described a chat with a lot of branches (edits and regenerations) and got no answer on the forum, so a Support ticket is the only route we found.

What Support asks you to send

In the September 2026 thread OpenAI Support asked for a sanitized HAR file (a recording of the browser's network traffic), the conversation ID or request ID, the exact time in UTC, your browser and version, and your OS or device, sent to support@openai.com. They said the conversation URL and error ID are usually enough for them to find the chat. Don't delete the broken chat while you wait.