{"version":"2.1.261","anchor":"new-not-fetchedno-response-diagnostics-for-organization","canonical_anchor":"new-not-fetchedno-response-diagnostics-for-organization","heading":"New 'not fetched'\/'no response' diagnostics for organization policy retrieval","tier":"notice","area":"Org Policy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/new-not-fetchedno-response-diagnostics-for-organization","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### New 'not fetched'\/'no response' diagnostics for organization policy retrieval\n\nDiagnostics now explain in detail why org policy couldn't be fetched, with specific failure reasons.\n\nDiagnostics gain a new status entry explaining why organization policy couldn't be fetched, covering cases such as a third-party provider, a custom base URL, no auth, a missing OAuth inference scope, or a Pro\/Max account. It also reports why a fetch attempt failed, distinguishing `auth_failed` (including HTTP 403 with proxy guidance), timeout, `network_error`, `parse_failed`, `spurious_304`, and `request_failed` (with specific guidance for HTTP 404, 304, and 407), and notes that the fetch is 'Retried hourly while Claude Code runs; restart to retry now.'\n\n- Area: Org Policy\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}