{"version":"2.1.224","anchor":"settings-presence-checks-can-read-through-the-newer-settings","canonical_anchor":"settings-presence-checks-can-read-through-the-newer-settings","heading":"Settings presence checks can read through the newer settings store","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/settings-presence-checks-can-read-through-the-newer-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Settings presence checks can read through the newer settings store\n\nChecks for explicitly set settings keys can now read from the newer settings store.\n\n**What**\n\nThe check for whether a key such as `cleanupPeriodDays` is written explicitly in a settings file is now asynchronous and can be given a reader, in which case user settings come from the newer store instead of the file on disk. A read failure is logged and treated as unknown rather than as absent, and the retention cleanup gate became async to match.\n\n**Evidence**\n\n`rawSettingsKeyPresence: v5 user-settings read failed`\n\n- Area: Settings\n- Names: `cleanupPeriodDays`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}