{"version":"2.1.261","anchor":"policy-limits-404-now-distinguished-as-route-missing-from","canonical_anchor":"policy-limits-404-now-distinguished-as-route-missing-from","heading":"Policy-limits 404 now distinguished as 'route_missing' from a transient cache miss","tier":"notice","area":"Org Policy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/policy-limits-404-now-distinguished-as-route-missing-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Policy-limits 404 now distinguished as 'route_missing' from a transient cache miss\n\nA confirmed 404 on the policy route now shows a distinct 'policy route not served' message.\n\nPolicy-limit resolution for gated features like Remote Control, artifacts, and `allow_cobalt_plinth` now distinguishes a confirmed 404 on the policy route (`route_missing`) from an ordinary transient cache miss, showing \"policy route not served\" instead of generic unverified-policy messaging in the confirmed-404 case.\n\n- Area: Org Policy\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}