{"version":"2.1.282","anchor":"managed-settings-new-error-when-no-served-setting-can-be-ap","canonical_anchor":"managed-settings-new-error-when-no-served-setting-can-be-ap","heading":"Clearer error when none of your organization's managed settings can be applied","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/managed-settings-new-error-when-no-served-setting-can-be-ap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Clearer error when none of your organization's managed settings can be applied\n\nWhen the policy server sends settings but none of them can be applied, the error now says so and asks your administrator to fix them\n\n**What**\n\nManaged settings are settings your organization's administrator sends to Claude Code from a policy server. When that server sends settings but none of them can be applied as written, the error now says exactly that and asks you to have your administrator fix them. Before, this case showed a general message saying the policy could not be loaded.\n\n**Why**\n\nThe old message looked like a network problem. Administrators now get an accurate reason and know the settings themselves need fixing.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}