{"version":"2.1.242","anchor":"remote-settings-and-helper-consent-mirrored-into-a-second-st","canonical_anchor":"remote-settings-and-helper-consent-mirrored-into-a-second-st","heading":"Remote settings and helper consent mirrored into a second store","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/remote-settings-and-helper-consent-mirrored-into-a-second-st","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Remote settings and helper consent mirrored into a second store\n\nRemote settings and helper consent are now also mirrored into a second in-process store.\n\n**What**\n\nSaving remote settings, saving or deleting helper consent, and clearing the cached settings now each also write the new value, or null on deletion, into a second in-process store. Bookkeeping only, with no visible effect.\n\n**Details**\n\n- Applies on both the storage-backend and the plain-file paths.\n- The cache clear is now only recorded when the backend delete reports success, and the file-delete path swallows only a missing-file error rather than everything.\n- Both mirror writes sit behind a pair of conditions that nothing in this build decides.\n\n**Evidence**\n\n`Remote settings: Saved helper consent via storage backend`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}