RU

“Unknown error” in ChatGPT: length limit or server glitch — and a workaround that actually works

Published: 2026-11-16 · Author: AI Release · @ai_release1
“Unknown error” in ChatGPT: length limit or server glitch — and a workaround that actually works

⚡ The gist

On November 9, 2026, two ChatGPT conversations in different projects stopped opening almost simultaneously: first a warning about the conversation length limit popped up, then it was replaced by “Unknown error” with a “Start new chat” button. Thread author nicolo.campagna immediately suspected a bug rather than a real limit, and asked whether anyone had seen the same sequence. Over 11 replies and 378 views, the thread split into two debates: where the limit ends and a server-side failure begins, and what to do with an already “dead” chat. The 17 likes went mostly to the workaround someone found.

🗣 What participants are saying

nicolo.campagna described the key asymmetry: other conversations, including longer ones, kept working, and new chats and branches were created without issue. In his view, this is a “possible bug, rather than an actual conversation-length limit.” On November 11 he added that the same thing happened in a newer chat within the same project — after he had already created a replacement for the broken conversation. In other words, the problem reproduces even on “fresh” threads.

jack.soemmerly confirmed: “Me as well.” According to him, the HAR file and console output point to internal server-side processing of conversations; it’s been going on for 4–5 days, he filed a ticket and promised to report back when there’s an answer. Later he described the failure scenario: a new chat in a project, a prompt with a large context, code, or archives, 2–5 messages — and then “Connection lost. Waiting for the full reply” appears, followed by “Unknown Error.” After that, the conversation won’t load.

me108 adds an economic angle: he’s on a Pro subscription and uses ChatGPT as a project manager in development — drafting design documents and specs. “The conversation length feels increasingly shorter and shorter,” he writes, clarifying that this is already the 4th or 5th fork of the chat, and in the latest fork he couldn’t continue. His description of the workaround repeats the steps: a Share link for the entire conversation, open it in a new tab, wait for it to load, send a prompt — “ChatGPT answers normally with full chat history and context awareness.”

nicolo.campagna tested the workaround on a chat that was completely dead and confirmed: the link opened in a new tab, and a test message created a working copy with the history intact. He also noted separately that the restored conversation continued working with his existing project context.

OpenAI_Support thanked jack.soemmerly for the workaround and noted that nicolo.campagna and me108 had confirmed their history was restored in a new copy. According to the support rep, OpenAI logged a private incident involving ChatGPT conversation errors on November 9, and anyone still affected was told to create a Share link, open it in a new tab, and send a prompt.

jack.soemmerly pushed back on that framing: “I can see that this issue isn’t isolated to the incident” — in his observation, there are forum threads about the same problem going back as far as last year. He directly asked whether it would be fixed.

⚖️ Where they agree, where they split

There is common ground, and it’s practical: the symptom reproduces for several people, and the Share-link workaround worked for at least three participants — jack.soemmerly proposed it, nicolo.campagna and me108 confirmed it, and OpenAI_Support logged the confirmations. Nobody in the thread disputes either the “length warning → Unknown error” sequence itself or the fact that recovery via a new tab works.

The real point of conflict is the cause and the scope. The thread author and me108 read what’s happening as a premature length limit or a buggy implementation of it; jack.soemmerly, citing the HAR file and console, points to server-side conversation processing and insists the problem predates and extends beyond the November 9 incident. Support responds by pointing to that specific closed incident. There’s no consensus in the thread on the root cause — and no numbers that would settle it.

🧪 What to check yourself

🔗 Sources

OpenAI Community — [Bug] Two ChatGPT conversations simultaneously became unusable — “Unknown error / Start new chat”

Disclaimer: this is a summary of a discussion, not facts verified by our editors. The opinions belong to the participants; the numbers belong to whoever cited them.

🤖 AI summary
  • Date: 2026-11-16
  • Source: community.openai.com
  • Tags: AI, ChatGPT, OpenAI
  • Key facts:
    • On November 9, 2026, two ChatGPT conversations in different projects stopped opening almost simultaneously: first a warning about the conversation length limit popped up, then it was replaced by “Unknown error” with a “Start new chat” button.
    • Thread author nicolo.campagna immediately suspected a bug rather than a real limit, and asked whether anyone had seen the same sequence.
    • Over 11 replies and 378 views, the thread split into two debates: where the limit ends and a server-side failure begins, and what to do with an already “dead” chat.
    • The 17 likes went mostly to the workaround someone found.
    • nicolo.campagna described the key asymmetry: other conversations, including longer ones, kept working, and new chats and branches were created without issue.
    • In his view, this is a “possible bug, rather than an actual conversation-length limit.” On November 11 he added that the same thing happened in a newer chat within the same project — after he had already created a replacement for the broken conversation.
    • In other words, the problem reproduces even on “fresh” threads.
    • jack.soemmerly confirmed: “Me as well.” According to him, the HAR file and console output point to internal server-side processing of conversations; it’s been going on for 4–5 days, he filed a ticket and promised to report back when there’s an answer.
#AI#ChatGPT#OpenAI
← PreviousTaiwan warns chipmakers of detention risk in China: 470 casesNext →Anthropic buys 1.7GW of gas power to jump the queue

Source: community.openai.com · post in Telegram