{"version":"2.1.248","anchor":"remote-managed-settings-log-why-every-fetch-failed","canonical_anchor":"remote-managed-settings-log-why-every-fetch-failed","heading":"Remote managed settings log why every fetch failed","tier":"internal","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-managed-settings-log-why-every-fetch-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote managed settings log why every fetch failed\n\nManaged-settings fetch failures now log a categorised reason, and consent files are size-limited.\n\n**What**\n\nFetch failures, retries and falls-back-to-cache now record the error as a kind, or a kind and HTTP status, through one shared formatter, and the 401 force-refresh path logs before retrying. The consent records file is also read with a bounded range read and rejected as unreadable when it exceeds a size limit.\n\n**Evidence**\n\n`Remote settings: Consent records file exceeds `\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}