2026-07-20 - Personalisation Cache Overwrite Fixes¶
Release¶
AgileData.io - Settings That Stick: Personalisation Cache Race Conditions Resolved
Two related bugs were causing personalisation settings to be silently overwritten, making it appear that preferences weren’t being saved correctly.
The first issue occurred at startup: the general startup cache write was running after personalisation had loaded and overwriting it with an empty object. This meant any preferences set in a previous session were erased the moment the application initialised. Personalisation now has its own exclusive write path that cannot be clobbered by the startup cache.
The second issue occurred when a user navigated away from a page before the Firestore write completed. The in-progress write was being abandoned rather than completing, losing the preference update. The write now completes correctly regardless of navigation timing.
What was happening:
Startup cache write was overwriting personalisation data with an empty object on page load
Navigating away before a Firestore write completed silently discarded the preference update
What this means for you:
Personalisation settings are saved reliably and not reset on each visit
Preferences changed just before navigating away are no longer lost
Last Refreshed¶
Doc Refreshed: 2026-07-20