{"version":"2.1.242","anchor":"startup-can-wait-on-a-remote-managed-settings-refresh-with-a","canonical_anchor":"startup-can-wait-on-a-remote-managed-settings-refresh-with-a","heading":"Startup can wait on a remote managed-settings refresh, with a deadline","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/startup-can-wait-on-a-remote-managed-settings-refresh-with-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Startup can wait on a remote managed-settings refresh, with a deadline\n\nStartup can briefly wait for refreshed managed settings, with a deadline so it never hangs.\n\n**What**\n\nA new startup step races a fetch of remote managed settings against a consent prompt and reports one of four outcomes: refreshed, failed, timed out, or consent pending, meaning a consent dialog is up so startup does not block on the fetch. When the deadline expires it records a `deadline_expired` telemetry event.\n\n**Details**\n\n- Telemetry event name: `remote_managed_settings_startup_await`.\n- Neither the event name nor the outcome strings exist in 2.1.241; this is a new path used only by managed and remote settings deployments.\n\n**Evidence**\n\n`remote_managed_settings_startup_await`\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}