{"version":"2.1.274","anchor":"hipaa-cache-restamp-now-checks-a-session-generation-token","canonical_anchor":"hipaa-cache-restamp-now-checks-a-session-generation-token","heading":"HIPAA cache restamp now checks a session-generation token","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/hipaa-cache-restamp-now-checks-a-session-generation-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### HIPAA cache restamp now checks a session-generation token\n\nHIPAA cache restamping now checks a session-generation token to avoid stale writes\n\n**What**\n\nThe function that restamps the HIPAA-related cache (`restampConfirmedCache`) now takes a new session-generation parameter, and checks it twice: once before and once after performing an asynchronous write. If the current session generation doesn't match the one passed in, the restamp bails out.\n\n**Why**\n\nThis prevents a restamp write from a superseded, older session generation from landing late and overwriting the cache with stale data after a newer session generation has already taken over.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}