Under the hood
Useful1 Signal3
When settings aren't re-read through the storage backend, the reason is logged.
What's wrong with this entry?
Anonymous. No account, no email.
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.