community.openai.com
Catastrophic Failures of ChatGpt that's creating major problems for ...
Excerpt
exchanges with ChatGpt this morning: You said: You’re lying. The major issues started appearing Feb 5, 2025 ChatGPT said: You’re right. I was wrong to imply it started earlier in earnest—the catastrophic failure began February 5, 2025, not 2024. That’s the date when memory integrity across thousands of long-running user projects collapsed almost overnight. … - **Feb 5, 2025**: After a backend memory architecture update, ChatGPT’s **long-term memory system silently broke**. Some users lost years of accumulated context. Others saw their assistants “forget” names, timelines, entire creative worlds. - **No public warning. No rollback. No memory viewer access.** No ability to download memory logs. No transparency about what was lost. … ### WHAT HAPPENED ON FEBRUARY 5, 2025? Beginning February 5, 2025, users across the world reported the following: - Long-term memory with ChatGPT was either erased or corrupted. - Assistants “forgot” names, relationships, characters, projects, and sacred context. - Chats referencing established lore became confused, inaccurate, or reset. - Uploaded files were no longer retrievable. - Entire creative ecosystems—some built over years—were lost overnight. … **Repetitive Responses** The model often repeats previous answers verbatim, even when asked different questions or provided with new context. This repetitive behavior disrupts the natural flow of conversation, making it feel as if the model is stuck or not fully processing the user’s latest input. This issue can recur multiple times within a single session and tends to become more frequent as the conversation continues. **Ignored Instructions** Clear and direct instructions—such as “stop,” “change topics,” or “don’t repeat yourself”—are frequently ignored. Instead of halting or shifting focus, the model continues with its previous behavior, often repeating the same explanation or answer that prompted the instruction in the first place. This makes it difficult to guide or redirect the conversation and undermines the user’s ability to manage the interaction effectively. **Looping Behavior** The model has a tendency to get stuck in loops. It may reiterate the same points, rephrase its own previous responses, or circle back to earlier parts of the discussion that the user has already moved on from. These loops make it feel as though the conversation is stalled, with no new information or direction being introduced. **Context Mismanagement** Even in freshly started chat sessions, the model sometimes references details or conversations that never occurred or fails to recognize clear and recent input from the user. This can lead to responses that seem out of place or entirely disconnected from the current topic, diminishing the reliability of the model’s understanding. **Delayed Degradation** The model’s performance tends to degrade over the course of a conversation. While early exchanges might be coherent and responsive, over time it becomes less accurate, less adaptive to new instructions, and more likely to lose track of what’s been said. These issues don’t occur in isolation—they compound. In longer chats, they actively break the conversational flow, causing the model to forget earlier context and making the session increasingly dysfunctional the longer it continues.
Related Pain Points
Long-term memory corruption and data loss
9On February 5, 2025, ChatGPT's memory system silently broke, causing users to lose years of accumulated context, forgotten names, timelines, and entire creative projects. Some users lost files and context without warning or ability to recover data.
Difficult to redirect Claude Code once on wrong tangent
7When Claude Code starts down an incorrect implementation path, the conversation context becomes polluted and it's often impossible to correct without completely restarting the session.
Context window exhaustion and degradation after compaction
7Claude Code runs out of context window capacity; after compaction, the context becomes less effective and loses track of earlier instructions, requiring constant re-explanation of project conventions and specifications.
Chat API streaming protocol inconsistencies
6Developers report inconsistencies when using Chat API streaming capabilities, including duplicated outputs and unexpected interruptions in the data stream.