ChatGPT Says “Could Not Load This ChatGPT Conversation” on Every Old Chat? Why It Is Not Deleted, and the Fixes Users Report Working (October 2026)

Short answer: “Could not load this ChatGPT conversation” has been hitting old chats since late September 2026, and on October 15 some users reported every past conversation failing on every device at once. Your chats are almost never deleted: they still show in the sidebar, and the same chat usually opens in the iOS or desktop app, or in a tab that was already open. The fixes that users report working are, in order, pressing Try again a few times, opening the chat in another app, and exporting your data to get the text out. Clearing cache, logging out and switching browsers mostly do not help.

The error is short and the panic is not. You click a chat you have used for weeks, the sidebar still lists it, and the page says it could not load. New chats work fine, which makes it feel like the old one is gone.

It is usually not gone. Here is what the reports from OpenAI’s own forum say, what OpenAI’s status page shows for October 15, and the order in which to try things.

Based on OpenAI Developer Community bug threads and the OpenAI status page as read on October 16, 2026. These are user reports plus OpenAI support replies, not an official root-cause statement; OpenAI had not published one at the time of writing.

Contents

What does “Could not load this ChatGPT conversation” actually mean?

The “Could not load this ChatGPT conversation” error means the ChatGPT client could list a chat in your sidebar but failed to fetch its message contents from OpenAI’s servers, which is why the same conversation can still open in another app or in a tab where it was already loaded (OpenAI Developer Community, October 15, 2026).

The October 15 report is the clearest description of the bad case. One user found that 100% of their old conversations failed on Chrome, Chrome Incognito, other browsers, the ChatGPT desktop app and the Android app, across different networks. New conversations worked. Old conversations that were already open in existing Chrome tabs kept working.

That last detail is the useful one. The messages exist. The problem is the request that fetches them.

The main bug thread, open since at least October 5, lists the companions you may also see: “Connection interrupted. Waiting for the complete answer,” a “too many requests” style message, a conversation list that will not load, and search that cannot find older chats (OpenAI Developer Community bug thread).

Is it an outage, or is it just my account?

On October 15, 2026, OpenAI’s status page logged an incident titled “Widespread feature degradation” that was later marked fully recovered, but neither that entry nor the other incidents listed for October 13–15 mention conversation loading or chat history by name (OpenAI status history).

When I checked the status history for the three days around the reports, I found five entries: degraded performance for GPT-6.1 Sol in Codex and Work mode on October 13, degraded Codex and ChatGPT Work on October 14, limited availability of two image models the same day, the “widespread feature degradation” on October 15, and delayed cost data in the Compliance API that evening.

So the pattern is: a real service wobble on the 15th that lines up with the “all my chats failed” reports, sitting on top of a slower-burning bug that users had been reporting for two weeks before it.

Honestly, that is the frustrating part. If it were a clean outage you would wait an hour. Because the forum reports stretch back to late September, with a related GitHub issue filed against the Codex repository on September 26–27, some people have been seeing it intermittently for weeks.

Fixes in the Order Users Report Them Working

None of these is official. They are what people in the bug threads say worked, ranked by how often and how reliably.

Step What to do What users report
1. Try again, a few times Click the Try again button or reload the page. Wait a few seconds between attempts. Intermittently works, sometimes after many attempts. One user noted the button later gained a long cooldown.
2. Open it somewhere else Open the same chat in the iOS app, the desktop app, or a browser tab that already has it loaded. The October 8 report: web failed in Edge, the identical chat opened on iOS. October 15: already-open tabs kept working.
3. Private window, extensions off Open chatgpt.com in an incognito or private window with all extensions disabled. Suggested by OpenAI support on October 6. Rules out an extension; did not fix the October 15 case, where incognito also failed.
4. Check Archived chats Settings, then Data controls, then Archived chats. Unarchive and reopen. An early-October report said regular chats recovered before archived ones did.
5. Export your data Settings, then Data controls, then Export data. OpenAI emails a download link. Does not fix the error, but gets the text of every chat out of the account. See the section below.
6. Contact support with a HAR file Record a browser network log of the failure and email it with the chat URL and timestamps. What OpenAI support asked for on October 6 and 12. Slow: one user waited a week.

Compiled from OpenAI Developer Community threads 1403341, 1404265 and 1406548 and OpenAI support replies in them, October 5–15, 2026.

What users say did not help: hard reloads on their own, signing out and back in, switching browsers, clearing cache. If you have done those three times already, stop. Move to step 2 or 5.

Why does the same chat open on iOS but not on the web?

A ChatGPT conversation that shows “Could not load” on the web but opens normally in the iOS app, as a user reported on October 8, 2026, indicates the chat data is intact on OpenAI’s side and the failure is in how the web client requests or renders it (OpenAI Developer Community, October 8, 2026).

The apps and the website use different builds. A change that breaks loading in one does not necessarily break it in the other, which is why “try another client” ranks so high in the table.

It also explains why the October 15 case felt worse. That user tried Chrome, the desktop app and the Android app and all failed. Whatever happened that day was not limited to the web build, which fits the status-page incident rather than the older bug.

Hands typing on a smartphone, illustrating opening an old ChatGPT chat in the mobile app as a workaround
OpenAI’s status page recorded a “Widespread feature degradation” incident on October 15, 2026, the same day users reported every old ChatGPT conversation failing to load.

How do I get the text out if nothing loads?

ChatGPT’s data export, found under Settings, then Data controls, then Export data, sends an email with a download link that includes your conversation history as files, and OpenAI’s help centre says the link expires 24 hours after it is sent (OpenAI Help Centre, exporting your data).

This is the step that turns a scary bug into an annoying one. The export is generated server-side, so it does not depend on the web client being able to render a chat. If the messages exist, they come out.

A few practical notes from doing this during an incident:

  • The email can take a while to arrive when the service is degraded. Request it once and wait rather than requesting it repeatedly.
  • The archive contains an HTML file you can open in any browser, plus JSON. Search the HTML file for a phrase you remember from the missing chat.
  • Download it within the 24-hour window, and keep the file. It is also your backup for the next time.

If you only need one answer from one chat, a cheaper route is an already-open tab. Do not close it until you have copied what you need.

What should I send OpenAI support?

OpenAI support replied in the main bug thread on October 6 and October 12, 2026 asking affected users to test in a private window with extensions disabled and then to email support with the conversation URL, timestamps including time zone, the browser or app version, and a HAR file recording the failed request.

A HAR file is a network log your browser can save from its developer tools while you reproduce the error. It shows support exactly which request failed and with what response. Without it, the ticket tends to bounce back asking for it, which is what one user described after waiting a week.

Two small things make the ticket faster. Share the support case ID, not the chat contents, if you post publicly; OpenAI’s moderator asked for that on October 12. And include whether the same chat opens in another app, because that single fact tells support whether it is a data problem or a client problem.

If your issue is the related one where the Android app says content is unavailable in this version, that is a different bug with its own fix, covered in our guide to the “content is unavailable in this version of the app” error.

Tips

  • Keep one tab with your most important chat open while the bug is active. Loaded tabs kept working on October 15.
  • Export your data now, before you need it. The link lasts 24 hours; the file lasts as long as you keep it.
  • Check status.openai.com before troubleshooting. If there is an active incident, the fix is waiting, not reinstalling.
  • When you report it, note the exact minute and your time zone. Support asked for that specifically.

Warnings

  • Do not delete and reinstall the app expecting it to restore chats faster. It does not change what the server returns.
  • One user suspected that hammering reload during a failed response lost unsaved work. Unverified, but wait a few seconds between retries.
  • The export email link expires after 24 hours. Download it the day it arrives.
  • Never paste a HAR file publicly. It can contain session tokens. Send it only to OpenAI support.

FAQ

Does the Could not load this ChatGPT conversation error mean the chat was deleted?

Almost never. Deleted chats disappear from the sidebar entirely. A chat that is listed but will not open is a loading failure, and users have confirmed the same chats opening in another app or appearing in a data export.

Does the error affect ChatGPT Free, Plus and Pro accounts equally?

Reports in the bug threads come mostly from paying users, including Pro and ChatGPT Work, but nothing in the reports ties the error to a plan. It appears to be a client and service issue rather than an account-tier issue.

Can I recover a chat that fails to load on every device?

Yes, usually through the data export under Settings and Data controls, which is generated on OpenAI’s servers rather than in the app. If the export also lacks the chat, that is the point to raise a support ticket with the chat URL.

Sources

📌 Hub guide: For every fix, buying decision, and work-from-anywhere setup in one place — see the Tech & Digital Hub.

Fact-checked against OpenAI Developer Community bug threads, the OpenAI status page and OpenAI’s help centre as of October 16, 2026. User-reported workarounds are not guaranteed; this is not official OpenAI guidance.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *