{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihr7usctv6r2nq5uwf37vbxzuoacbyp5i4nmuiz4snbhj2kzo4weq",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mozgv2hhddy2"
  },
  "path": "/t/unarchiving-issue-troubleshooting-failed/1384555#post_1",
  "publishedAt": "2026-06-24T07:49:38.000Z",
  "site": "https://community.openai.com",
  "textContent": "I’m trying to determine whether anyone else has seen a similar issue with older, very long archived ChatGPT conversations.\n\nI have a number of archived conversations that had previously reached the conversation limit. Around February/March 2026, many of them became partially inaccessible.\n\nThe behavior differs by client. On Web/Android, affected conversations show \"The conversation is too long, please start a new one.”\n\nOn iOS, some of the same conversations can still appear through Search and may open there, but unarchiving fails every single time.\n\nThe affected conversations still appear in my data export, so they do not appear to be fully deleted. The issue looks more like an inconsistent conversation/archive state, metadata, or loading problem affecting older long conversations.\n\nMy goal is not to continue these conversations. I’m just trying to access the existing history so I can copy/save needed information and then clean up/delete the archived chats.\n\nThe export only helps partially, because it does not fully replace the in-product conversation view, especially where edited/regenerated paths inside the same conversation matter.\n\nHas anyone else run into older long archived conversations becoming inaccessible or impossible to unarchive like this? If so, were you able to recover access, or was export the only usable workaround?",
  "title": "Unarchiving issue. Troubleshooting failed"
}