{"version":"2.1.232","anchor":"remote-managed-settings-failures-report-why","canonical_anchor":"remote-managed-settings-failures-report-why","heading":"Remote managed settings failures report why","tier":"internal","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-managed-settings-failures-report-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote managed settings failures report why\n\nFailed managed-settings fetches now record a structured reason visible in debug logs.\n\n**What**\n\nWhen Claude Code cannot fetch centrally managed settings, it now records a structured reason alongside whatever settings it has, so debug logs say what actually went wrong instead of just that a fetch failed.\n\n**Details**\n\n- The failure carries an error kind, a message, and optionally the HTTP status and whether a gateway pin mismatched.\n- The error kind is named in the debug output on both the stale-cache path and the no-cache path.\n\n**Evidence**\n\n`Remote settings: Fetch failed (`\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}