{"version":"2.1.261","anchor":"new-policy-route-not-served-diagnosis-for-remote-control-o","canonical_anchor":"new-policy-route-not-served-diagnosis-for-remote-control-o","heading":"New \"policy route not served\" diagnosis for Remote Control org-policy fetch","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/new-policy-route-not-served-diagnosis-for-remote-control-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### New \"policy route not served\" diagnosis for Remote Control org-policy fetch\n\nRemote Control now diagnoses when its policy route isn't being forwarded by a proxy or gateway.\n\nRemote Control's org-policy fetch (`\/api\/claude_code\/policy_limits`) now distinguishes a `route_missing` outcome from a generic cache miss. This case gets its own user-facing explanation pointing to a proxy or gateway not forwarding the path, its own telemetry reason (`policy_route_missing`), and its own denial-reason error subtype.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}