You'll notice
Useful2 Signal2
Startup can briefly wait for refreshed managed settings, with a deadline so it never hangs.
What's wrong with this entry?
Anonymous. No account, no email.
What
A 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.
Details
- Telemetry event name:
remote_managed_settings_startup_await. - 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.
Evidence
remote_managed_settings_startup_await
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Managed-settings review prompt dropped from the main UI
Both mention managed
-
v2.1.246
Remote managed settings can defer their consent prompt to the next interactive session
Both mention managed
-
v2.1.248
Telemetry on how OS-level managed settings are read
Both mention managed