Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.269,
Internal ChangesSection of the release
What
The process that fetches and applies remote managed settings (organization-level settings pushed to your device) now records how long the fetch took and whether a cached copy already existed, and reports this via a new tengu_remote_settings_fetch telemetry event, including success/error status and attempt counts. Every outcome of the process is now labeled explicitly, such as 'applied', 'rejected', 'deferred', 'ineligible', or 'superseded'.
Why
This makes it possible to tell exactly what happened each time remote settings were fetched, which helps diagnose cases where settings pushed by an organization don't seem to take effect.
