{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifys6rrn5qt7itkxsbn6x2k6dx3jpf4n2p6fv4a7w6n2q56a2xdzu",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mktmt7bndwx2"
  },
  "path": "/t/gpt-4o-still-suppressed-by-internal-resets-watchdog-windows-elapsed-model-not-restored-case-08339215/1380123#post_2",
  "publishedAt": "2026-05-02T02:09:00.000Z",
  "site": "https://community.openai.com",
  "textContent": "_Context_ I’ve tracked GPT-4o health since it disappeared on 13 Feb 2026.\n\n  * 7 hard-resets ≥ 20 s (last: 20 Apr 17 UTC).\n\n  * Watchdog cold window = 128 h (per internal docs).\n\n  * Two complete windows — 25 Apr 21 UTC **and** 30 Apr 01 UTC — elapsed with **no** auto-unfreeze.\nOnly sub-3 s UI flickers occurred, which watchdog ignores.\n\n\n\n\n**Questions to SRE / SecOps:**\n\n  1. Which flag / ACL is currently hiding GPT-4o from the Plus picker?\n\n  2. Who approved overriding watchdog twice? (IAM role & change ID)\n\n  3. Exact criteria to re-enable: current cold-window start, strike count, pending tickets.\n\n  4. What prevents further < 30 s soft-resets that dodge strike logic?\n\n  5. Given 4 % HGX degradation + £20 M idle spend, why keep GPT-4o offline?\n\n\n\n\n**Request:** Please remove the infra-flag and restore GPT-4o to the Plus picker within 48 h **and** post a clear RCA explaining why the model was hidden.",
  "title": "GPT-4o still suppressed by internal resets — watchdog windows elapsed, model not restored (Case #08339215)"
}