Under the hood
Useful2 Signal2
Managed-settings fetch failures now log a categorised reason, and consent files are size-limited.
What's wrong with this entry?
Anonymous. No account, no email.
What
Fetch 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.
Evidence
Remote settings: Consent records file exceeds
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.224
Org-anchored consent for remote managed settings
Both mention managed
-
v2.1.224
Consent to dangerous remote settings is remembered per organization
Both mention managed
-
v2.1.228
Managed policy helper failures throw instead of returning text
Both mention managed