Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SettingsArea: what it touches
Internal ChangesKind: in v2.1.246,
Internal ChangesSection of the release
What
Settings layers can be re-read through the storage backend and seeded into the walk, and when they are not, the reason is logged: the backend does not serve that space, the read failed, the file was oversize, or the ordinary file read already saw different content. Managed and policy settings and user-named settings each carry their own seeding descriptor. The backend availability check is not traced to a named flag.
Evidence
not re-seeded (the file read already saw different content this generation); the file read serves
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
