{"version":"2.1.269","anchor":"remote-managed-settings-fetch-gains-structured-telemetry-and","canonical_anchor":"remote-managed-settings-fetch-gains-structured-telemetry-and","heading":"Remote managed-settings fetch gains structured telemetry and 'resolution' outcome","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/remote-managed-settings-fetch-gains-structured-telemetry-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Remote managed-settings fetch gains structured telemetry and 'resolution' outcome\n\nRemote managed-settings fetches now log detailed telemetry and a clear outcome for every attempt\n\n**What**\n\nThe 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'.\n\n**Why**\n\nThis 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.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}