Skip to content

[ChatGPT Web][Sep 26–27] All chats intermittently blocked; loaded conversation disappears into error, Pro work blocked #48683

Open

Description

@tapperwijn89

What issue are you seeing?

I am a ChatGPT Pro subscriber. Access to my existing conversations is repeatedly failing during ordinary navigation, and this is now preventing me from completing website development work.

This is still happening on September 27, 2026, after repeated failures on September 26. By approximately 13:14 CEST on September 27, I had spent the morning trying to regain usable access to my conversations. During affected periods, every conversation I try to open is affected.

Symptoms

  • ChatGPT shows "Too many requests", with wording about temporarily limiting access to conversations to protect my data.
  • It also shows "Kan dit ChatGPT-gesprek niet laden" (Dutch for "Could not load this ChatGPT conversation").
  • A conversation can briefly display its existing contents and then replace them with the loading error again.
  • Leaving conversations open in separate tabs does not maintain reliable access: already-open conversations also become unusable over time.
  • Earlier episodes repeatedly cost approximately 10–20 minutes before chats could be opened again. The problem has continued into the next day rather than staying resolved.

Screen-recording observation

In an approximately 19-second recording from September 27, the contents of the same selected conversation appear twice and are then replaced by the loading error. The URL, sidebar and selected conversation remain present.

The recording contains private conversation content, so it is not attached publicly. It shows the visible UI failure, not an HTTP status code. A failed background refetch or HTTP 429 is a possible explanation, not a diagnosis established by this recording.

Environment and scope

  • Surface shown in the recording: chatgpt.com in Chrome on Windows, including a Work conversation.
  • Subscription: ChatGPT Pro.
  • Timezone for the observations above: Europe/Amsterdam, CEST (UTC+2).
  • Exact browser version and web build were not captured.
  • I noticed the problem after the recent interface update; that timing alone does not establish the cause.

What steps can reproduce the bug?

The failure is intermittent, so these describe the observed workflow rather than a guaranteed minimal reproduction:

  1. Open an existing conversation on chatgpt.com or switch to another existing conversation.
  2. During an affected period, observe the loading error or the temporary conversation-access restriction.
  3. Retry opening the same conversation: its contents can appear briefly and then disappear into the error again.
  4. Try other conversations: during these episodes, all conversations I attempt to open are affected.
  5. Leaving previously opened tabs in place does not provide a durable workaround.

What is the expected behavior?

Existing conversations should remain accessible during normal navigation. A user should be able to read and continue ongoing work reliably. Any temporary conversation-access restriction should explain its scope and recovery conditions clearly.

For a paid service, losing access to ongoing work for a second day is unacceptable. Please provide:

  • Public acknowledgement and triage of this specific conversation-access failure.
  • A supported mitigation for affected accounts.
  • A fix status or next update, and an estimated recovery time if one is known.

Additional information

Related reports reviewed before submitting:

This adds my independently affected account and the content-appears-then-disappears observation, with continued impact on September 27. If these reports share a cause, please link this evidence to the active tracking issue and identify that issue publicly.

Please treat this as a conversation-access/UI reliability report. No common root cause with model-message quotas or local Linux desktop startup failures has been established.

Activity

  1. added
    bugSomething isn't working
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Sep 27, 2026
  2. github-actions commented on Sep 27, 2026

    @github-actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  3. mamamatison commented on Sep 30, 2026

    @mamamatison

    Adding a Sep 30 datapoint relevant to the conversation-state / recovery side of this issue.
    I’m seeing conversations that are initially usable, then enter a long stall and become effectively unusable.
    One particularly strange state-sync symptom:

    • a conversation stalled;
    • I sent additional follow-up messages;
    • there was no response;
    • after reloading the page, some of those follow-up messages had disappeared from the visible conversation;
    • meanwhile, the assistant-side conversation state had advanced slightly;
    • the conversation then stalled again.
      In the same failure family I captured:
    • /backend-api/f/conversation/resume → 404
    • repeated /backend-api/conversation/ → 429
    • UI network error
    • temporary recovery after Retry
    • subsequent relapse into another stall
      This is also happening in brand-new conversations, so it is not limited to old or very large chat histories.
      Support has an escalated case with request IDs and sanitized HAR traces.
  4. tapperwijn89 commented on Oct 6, 2026

    @tapperwijn89
    Author

    Update — October 6, 2026

    This is still not resolved for me.

    I am continuing to get “Kan dit ChatGPT-gesprek niet laden” / “Could not load this ChatGPT conversation” when trying to open existing chats, and it is still preventing me from working normally in ChatGPT.

    At this point this has been affecting my account for roughly two weeks. I am a paying ChatGPT Pro subscriber and a large part of my ongoing work lives in existing conversations. Being unable to reliably open those conversations for this long is not a minor inconvenience anymore; it is a serious product reliability problem and it is actively disrupting my work.

    Retrying is not a meaningful workaround. Sometimes a conversation may load, and later the same conversation becomes unavailable again. I am still seeing the same failure today, October 6.

    Please provide an actual status update on this issue:

    • Is the underlying conversation-loading problem still being actively investigated?
    • Is there a known root cause for affected accounts?
    • Is there a supported mitigation beyond retrying/reloading?
    • Is there any ETA or next update for a permanent fix?

    After roughly two weeks of repeated failures, this is taking far too long for a paid product that I depend on for daily work.

  5. tapperwijn89 commented on Oct 6, 2026

    @tapperwijn89
    Author

    Correction to my previous update: my subscription is ChatGPT Pro, USD 200 per month. The conversation-loading issue has now been disrupting my normal work for roughly two weeks.

  6. Electricalpunk commented on Oct 7, 2026

    @Electricalpunk

    I'm also a pro subscriber and I have this a lot when multiple chats are running - mostly when they are taking forever to process a request - and it feels more and more like a limitation setting as if we're "bots" when running multiple chats rather then a bug. We're getting limited on our usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reportingsessionIssues involving session (thread) management, resuming, forking, naming, archiving

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions