{"version":"2.1.318","anchor":"memory-watcher-retries-writes-and-arms-delete-confirm-timer","canonical_anchor":"memory-watcher-retries-writes-and-arms-delete-confirm-timer","heading":"Memory sync handles stores whose writes will be retried","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/memory-watcher-retries-writes-and-arms-delete-confirm-timer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Memory sync handles stores whose writes will be retried\n\nMemory stores that report retryWrites now arm the delete-confirm timer and are no longer counted toward permanent-failure suppression\n\n**What**\n\nClaude Code can keep memory, saved notes that carry across sessions, in more than one store, and syncs them. Cowork memory sync now treats a store that reports `retryWrites`, meaning its failed writes will be tried again, differently.\n\n- The delete-confirm timer is now also started when any store reports `retryWrites`. Before, it started only in `corroborate` mode when some store had deletes put off for later.\n\n- A store with `retryWrites` has its count of permanent failures in a row reset and is skipped for that round. It no longer counts toward being suppressed.\n\n**Why**\n\nA store whose writes fail for a while but will be retried is no longer shut out as if it had failed for good, so failed memory writes get another chance.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}