Problem Solutions
ChatGPT Sidebar Not Loading Your Chat History? It's a Known Bug — Here's What Actually Helps
If your ChatGPT sidebar loads your most recent conversations and then stops — "Unable to load history," or a flat "Too many requests" — your chats are not gone, and you are not the only one seeing it. Since mid-September 2026, OpenAI's own community forum has filled with near-identical reports from Plus, Pro and Business users across browsers and devices. The short version: this is a bug in how ChatGPT loads your history, there is no setting on your side that fixes it, and the useful response is a small set of workarounds rather than the usual cache-clearing ritual.
What the bug looks like
The pattern repeats across dozens of forum threads. The sidebar loads the first screen of conversations — often the most recent twenty or so — and then fails when you scroll for older ones. Some users see "Unable to load history"; others hit HTTP 429 "Too many requests," and the longest-running thread documents 404, 500 and 503 errors and "Could not load this ChatGPT conversation" as well. Reports began around September 17–19, 2026, shortly after a web interface update, and were still being posted in mid-October. One consistent detail: having several ChatGPT tabs open makes it worse. Users who run three to five conversations at once describe the 429 errors arriving reliably, and reloading tabs appears to make things worse still — each reload fires off fresh history and reconnection requests that pile onto the same account-level rate limit.
Your chats are not deleted
This is the point the forum reports establish most clearly. In thread after thread, users confirm that the conversations the sidebar refuses to list open perfectly well through ChatGPT's search. The failure is in the sidebar's batched history loading — the request that fetches the next page of your conversation list — not in the conversations themselves. At least some affected users also report that the Windows desktop app loads the same history without problems while the web and mobile versions fail, which points the same way: the data is intact; one particular way of asking for it is broken.
What OpenAI has said
OpenAI staff responding in the forum have offered the standard narrowing steps — try another browser or network, disconnect a VPN or proxy if you use one — and have directed users to Support with a screenshot, browser version and the time and timezone of the failure. One clarification, noted in the forum from an October 1 support response, is more informative: OpenAI's fix for web history problems did not cover the "Too many requests" error. In other words, the company has treated the visible sidebar issue and the 429 failures as separate problems, and as of the most recent reports the 429 side remains open. OpenAI has not published a cause or a fix date.
What actually helps
None of the following repairs the sidebar. Each one either routes around it or stops making it worse.
Use search instead of scrolling. Searching for a keyword from the conversation you need is the workaround forum staff themselves point to, and users confirm it works while the sidebar does not. For most people this removes the urgency entirely.
Try the desktop app. If you mainly work on one computer, the desktop app has loaded history normally for users affected on the web. It will not help on your phone, but it covers the workday case.
Work in fewer tabs. The multi-tab pattern is the most reproducible trigger in the reports. Keeping one active conversation tab — and finishing or closing parallel ones — reduces the request bursts that trip the limit.
When the error appears, stop reloading. Refreshing feels productive and is counterproductive here: each reload generates more history requests against a limit you have already hit. Close the tab, wait a few minutes, and try once.
Export a backup if the history matters. Settings → Data controls → Export data (or OpenAI's Privacy Portal) produces a copy of your conversations; OpenAI says delivery can take up to seven days. It does not fix the live chat view, but it guarantees you hold the material whatever happens to your account.
What does not help
Users in these threads have already run the standard playbook for you: clearing cache, restarting the browser, incognito windows, different networks, different devices. The reports persist through all of them, which is what you would expect from an account-side problem. Upgrading from Plus to Pro did not resolve it either — the longest thread includes Pro users paying for the top tier with the same errors. The honest summary is that the fix has to come from OpenAI. Until it does, search is the reliable path to older work, and a data export is the reliable insurance.