{"version":"2.1.219","anchor":"memory-sync-no-longer-suppresses-pushes-for-the-whole-sessio","canonical_anchor":"memory-sync-no-longer-suppresses-pushes-for-the-whole-sessio","heading":"Memory sync no longer suppresses pushes for the whole session","tier":"notice","area":"Memory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/memory-sync-no-longer-suppresses-pushes-for-the-whole-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Memory sync no longer suppresses pushes for the whole session\n\nOne failed memory sync no longer silently stops all memory pushes for the rest of your session.\n\n**What**\n\nA single memory push failure used to silently stop all further debounced pushes and change notifications for the rest of the session; suppression now applies only to individual stores.\n\n**Details**\n\n- The per-scope memory watcher state dropped its `pushSuppressedReason` field, along with the session-wide suppression it drove (logged as \"suppressing retry for the rest of this session\")\n- The two early-returns keyed on that field are gone, and change events now always re-arm the debounce timer\n- Per-store suppression remains, carrying a `suppressedUntilMs` expiry, and the \"unlink cleared store suppression for\" recovery path is unchanged\n\n**Evidence**\n\n`memory-watcher[`, `pushSuppressedReason`\n\n- Area: Memory Sync\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}