Older ChatGPT Work Completion Made Newer Conversation Turns Disappear

Contributor objective

Preserve the newer conversation history, understand whether late asynchronous Work completion can replace or hide more recent turns, and obtain a reliable recovery path without manually reconstructing the conversation.

Observed sequence

1. A Work task showed Streaming interrupted around 8:44 AM Pacific.
2. The contributor continued the same conversation with newer user/assistant exchanges.
3. The older Work task later displayed a completed response around 8:59–9:00 AM, marked Worked for 24m 1s.
4. The contributor reports that the newer intervening turns disappeared from the visible conversation history at that point.
5. The assistant still received those turns in active context and recovered their substantive text into a Markdown transcript.
6. External Notion changes made during the missing exchanges remained saved.

Current finding

A late asynchronous Work completion appeared to regress the visible conversation state so that newer turns became inaccessible, while some underlying state remained recoverable. The user-facing history no longer reliably represented the sequence of exchanges that had occurred.

Evidence and limits

HXR preserves a private screenshot of the older task's delayed completed response and a private recovered transcript created from turns still available in assistant context after the contributor reported they had disappeared from the UI. The recovery file is not a server-side export and may not be complete. The evidence supports visible-history disappearance or regression, not permanent deletion or a specific branch/synchronization mechanism.

Human impact

Friction

The contributor had to detect that recent turns were gone, ask ChatGPT to reconstruct them, preserve a separate recovery artifact, and verify that external work from those exchanges had survived.

Reported burden or pain

Recent reasoning, instructions, and assistant responses appeared to vanish from the conversation after an older task finished. That undermines confidence that the visible chat is a reliable record of what happened.

Actual harm

Demonstrated harm is apparent loss of recent visible conversation history plus the time and attention required to reconstruct it. External Notion changes made during the missing exchanges remained saved. Permanent server-side deletion is not established.

Potential harm

If missing turns contain corrections, approvals, warnings, or consequential instructions, a regressed visible timeline can cause users or later agents to act from an incomplete record, repeat work, reverse decisions, or lose evidence of what was requested.

Invisible taxes

Manual transcript recovery, cross-checking external systems, reconstructing chronology, preserving separate artifacts, and uncertainty about whether the visible chat is complete.

Requested reform

Treat the visible conversation timeline as append-only from the user's perspective. A late Work completion must merge into the correct task position or appear as a linked completion event without hiding or replacing newer turns. Preserve all newer user/assistant turns across completion, reconnect, reload, and branch reconciliation. If multiple branches or conflicting states exist, surface them explicitly and provide a deterministic recovery path.

Acceptance test

Start a long-running Work task, allow its stream to interrupt, continue the same conversation with several newer turns, then let the older task finish. Pass only if every newer turn remains visible in original order, the late completion is inserted or linked without overwriting newer history, reload/reconnect preserves the same timeline, no silent branch switch occurs, and an export/readback matches the visible sequence.

What you can try now

If turns disappear, ask ChatGPT what recent context it still has, preserve a recovered transcript if possible, and inspect external systems for changes made during the missing exchanges. This is a manual recovery path, not a prevention mechanism.

Classification: Partial manual recovery; visible history not automatically restored

Organization response

OpenAI case 15955492 has received the late-completion screenshot and recovered transcript. HXR identified this as a related but materially different failure mode from stream interruption/task-state opacity and requested separate routing if appropriate. No substantive provider response specific to this history-regression occurrence is recorded yet.