{"version":"2.1.274","anchor":"policy-helper-managed-settings-refresh-now-tracks-failure","canonical_anchor":"policy-helper-managed-settings-refresh-now-tracks-failure","heading":"Policy-helper failure tracking avoids duplicate tier-change announcements","tier":"internal","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/policy-helper-managed-settings-refresh-now-tracks-failure","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Policy-helper failure tracking avoids duplicate tier-change announcements\n\nClaude Code now tracks managed-settings policy-helper failures by type so it only announces a tier change once, not on every retry.\n\n**What**\n\n- The policy helper (which manages settings pulled from a remote\/managed source) now remembers the last failure code it saw and only announces a tier change when the failure changes, not every time it fails.\n\n- `apply()` and `retireState()` reset the tracked failure (and reset `selectedEntry` when retiring).\n\n- The mid-session re-check also announces a tier change when the failed config itself changes, not just when other conditions change.\n\n**Why** Previously, a stuck policy-helper failure could re-trigger the \"tier changed\" announcement on every retry tick, creating noise. Now it fires once per distinct failure, giving a more accurate signal about when something actually changed.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}