ChatGPT “Conversation Not Found” and “Error in Message Stream”: What OpenAI Says and What Users Report

Short answer. We found no OpenAI Help Center page that documents either message. None of the six ChatGPT help pages we read contains “Conversation not found” or “Error in message stream,” and the Help Center’s own search was not working when we tried. The one status incident we found with the stream wording, in June 2025, ended in a rollback. Everything else comes from user reports, which are unverified, and no reply we read from an OpenAI-labelled account documents what either message means. One calls the stream message a generic error with several possible reasons, and one names an unusable Project source as the cause of a related Project failure.

Key takeaways

Key takeaways

1. Neither message is in OpenAI’s help pages. The nearest material is a missing-chat checklist and a list of generic errors.
2. The one status incident we found that names the stream message had a stated impact window of about 25 minutes on June 11, 2025. None of the 112 incidents in our July to October 2026 copy has “message stream” or “not found” in its title.
3. Of 104 forum threads we read in full, 62 contain a report of one of the two messages: 22 the first, 40 the second. Twenty-four of those 62 were opened in 2026.
4. Replies from accounts labelled OpenAI Support ask for details or say a fix shipped for a “related” problem. None documents what either message means.
5. No source says whether a chat is lost. Check status, run the documented checklist, then contact Support with a HAR file.

What do OpenAI’s help pages cover?

We read six pages in a browser on October 13, 2026. Each is real guidance; none contains either message.

What do forum threads report about “Conversation not found”?

Unverified user reports. On October 13, 2026 we ran twelve searches on community.openai.com and read in full, through its JSON endpoint, the 104 threads that matched either phrase, close variants or “Unable to load conversation.” Sixty-two contain a report of one of the two messages; the rest did not, or were excluded by hand. Fifteen of those use the plain wording, from April 18, 2023 to August 29, 2026. Seven more, all opened November 9 to 24, 2023, use “Message in conversation not found.” Dates are UTC.

• Temporary chats (September 2024 to August 2026). Three threads opened on September 7 and 9, 2024 describe the message on the second message of a temporary chat. One poster said it was fixed on September 10, 2024. The largest, with about 15,800 views, drew new “still happening” posts in April 2025, August 2025, January 2026 and June 2026. In August 2026 an Android poster said switching apps and returning produced it. OpenAI’s temporary chat page documents that an unsaved chat cannot be reopened, not the message.
• Custom GPTs and uploads (November 2023). Posters said the chat stopped after a second or later message, often with uploaded files. Some said refreshing after every response kept it alive; others said it did not, and two said a refresh removed earlier messages.
• Long Project chats and migration (May and August 2026). One poster described split and “continue” chats in long Project conversations. Another said that after a personal workspace was migrated to a Business workspace on May 11, 2026, one conversation returned the message and a 404.
• Other reports. A blank chat after tapping an app notification (May 2, 2025); a chat gone after a 404 (October 7, 2024); a chat that vanished while the model was thinking (August 2025, in a thread about the GPT-5 launch).

Reported triggers differ, and nothing shows a shared cause. Several reports add that the chat was missing from history. No OpenAI source says the message means a chat was deleted or lost.

What do forum threads report about “Error in message stream”?

Unverified user reports. Forty of the 62 threads carry the stream message. By the year each was opened: 4 in 2023, 6 in 2024, 9 in 2025 and 21 in 2026. The searches are not exhaustive, so these counts show no trend.

• Project chats (September 7 to October 10, 2026). The largest Project thread has 40 posts. Posters said Chat inside one Project failed, even for a one-word prompt, while Work and chats outside the Project still worked for several of them. Refreshing, clearing the cache, incognito windows, other browsers and devices, and signing out did not help them. Workarounds, with mixed results: moving a chat out of the Project, renaming it and refreshing, moving it to a new Project, clearing and restoring sources and instructions, and, on October 10, replacing two source files whose download returned a 404.
• Long chats and complex requests (June to October 2026). One poster saw it in a thread with more than 30 requests. Another said short prompts worked but extended-reasoning prompts stopped after minutes, while a friend’s account completed the same prompt.
• Android and Work mode (August to October 2026). Posters on Android, web and desktop reported it in long conversations with attachments. An October 8 poster saw it during image generation while the status page showed no problem.
• Earlier clusters. Image attachments on September 26, 2024; custom connectors on November 19, 2025, where posters said setups that worked the day before failed unchanged.

What have OpenAI-labelled accounts said?

We counted only accounts the forum labels “OpenAI Support” or “OpenAI Staff.” Of the 24 threads with either message in the title, six have a visible reply from one, a median of about 43 days after the thread opened (range 0.6 to 739). Five more of the 62 threads have a visible labelled reply (11 in all, median 28 days); none documents either message.

Do OpenAI status incidents match either message?

One we found does. On June 11, 2025, a degraded-performance incident listed ChatGPT as affected. OpenAI wrote that from 11:50 AM PDT (18:50 UTC) users noticed more stream errors, that it rolled back, and that recovery was complete at 12:15 PM PDT (19:15 UTC): 25 minutes.

Method for 2026. Our copy of OpenAI’s status incidents holds 112 that started between July 12 and October 9, 2026 (retrieved October 10). It stores titles and affected components, not update text, and we did not search status history before July 2026; the June 2025 incident came from a web search. It has one more incident than the 111 in the linked dataset post, and we did not trace which one accounts for the difference. A script searched titles. “Message stream,” “not found” and “history” matched none. “Conversation” matched 14, and all 14 list the Conversations component. In all, 36 incidents (32%) list it, with a median open time of 119 minutes, covering 31 of the 90 days.

We then checked whether an incident was open when each of eight 2026 threads was first posted (the seven with the message in the title inside the window, plus one with it in the body). None was; an incident was open in about 19% of the window’s hours, so zero of eight is unremarkable. A Conversations incident was open or had ended in the previous 24 hours for 5 of the 8, against about 35% of hours. That is a description, not a test: three of the five matches cluster around two September 22 and 23 incidents, so they are not independent, a result this extreme would occur by chance about 11% of the time, and a first post is not the moment the error began. To read the page, see our September count, what “resolved” means, the published dataset and the Work mode outage.

Documented, undocumented and reported, side by side

What can you do, using only documented guidance?

1. Check status.openai.com. OpenAI’s troubleshooting and network pages say to. An open incident is a possible explanation; none does not rule one out.
2. For the first message, run the missing-chat checklist. Confirm the account and workspace, search for a phrase from the chat, check Archived chats, refresh or sign out and in. Deleted chats cannot be restored, and an unsaved temporary chat cannot be reopened.
3. For the stream message, use the nearest documented steps. OpenAI lists none by name. Its pages suggest waiting 30 to 60 seconds, stopping and regenerating, starting a new chat or doing a hard refresh. These are generic, and we have not tested them on either message.
4. If it persists, contact Support with a HAR file recorded while reproducing it, console errors with timestamps, the model and the conversation URL.

Forum workarounds are not OpenAI guidance. Our five-step check covers choosing between waiting, status and Support.

What we could not verify

• A documented meaning or cause for either message.
• Whether one poster’s failure shares a cause with another’s.
• Whether any chat was lost. Posters say chats vanished; no OpenAI source confirms it.
• Whether the workarounds fix anything. Reports conflict, and some stopped working within a day.
• Whether status incidents explain reports, because our incident copy holds no update text.
• Whether our searches found every thread, or every labelled reply, since hidden posts are not visible.

Frequently asked questions