{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifcmatys2gjwa7ywtryz2n2b4oi3s3dqjg63daaxhkzriywr4mpja",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mnaww4qwlpe2"
  },
  "path": "/t/clarification-on-mcp-server-url-and-versioning-during-chatgpt-app-update-submission/1379705#post_7",
  "publishedAt": "2026-06-01T20:15:59.000Z",
  "site": "https://community.openai.com",
  "textContent": "adellibovi-edreams:\n\n> This approach worked well in the past: after submitting an app update, ChatGPT would eventually refresh the resource and start using the new version. Recently, however, we’re seeing resources being invalidated before the app submission is approved and rolled out. As a result, ChatGPT attempts to load a resource that is no longer available.\n\nI’m looking into this and will get back to you when I find something!\n\nZhou_Hui:\n\n> Our app has now been under review for two weeks and has still not been approved. It is possible that the review timeline has become longer again.\n\nUnfortunately yes, app submission volume has increased greatly in the past couple weeks and we are spinning up resources to handle it, but it will take 2-3 more weeks for them to come fully online sadly.",
  "title": "Clarification on MCP Server URL and Versioning During ChatGPT App Update Submission"
}