{"version":"2.1.304","anchor":"policy-settings-wait-telemetry-gets-an-outcome-field","canonical_anchor":"policy-settings-wait-telemetry-gets-an-outcome-field","heading":"Logs now say how waiting for managed policy settings ended","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/policy-settings-wait-telemetry-gets-an-outcome-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Logs now say how waiting for managed policy settings ended\n\nThe log entry for waiting on managed policy settings now records ok, timed_out or load_failed, and warns on any outcome that is not ok\n\n**What**\n\nWhen Claude Code waits for policy settings before starting MCP servers, its log entry now records an outcome. Policy settings are rules an organization sets centrally for its users. The possible outcomes are:\n\n- `ok`: the settings loaded\n\n- `timed_out`: the wait ran out of time\n\n- `load_failed`: the settings could not be loaded\n\nThe entry is logged as a warning for any outcome other than `ok`. Previously it was a warning only on a timeout, and it did not say which outcome happened.\n\n**Why**\n\nIt is easier to tell why managed settings did not load, and a failed load is no longer mistaken for a normal one.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}