{"version":"2.1.305","anchor":"team-memory-sync-backoff-keeps-pending-changes","canonical_anchor":"team-memory-sync-backoff-keeps-pending-changes","heading":"Team memory changes held back by a pause are now kept for retry","tier":"notice","area":"Memory","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/team-memory-sync-backoff-keeps-pending-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Team memory changes held back by a pause are now kept for retry\n\nWhen team memory syncing is paused after a failure, unsent changes now stay pending and are retried instead of being dropped\n\n**What**\n\nTeam memory is shared memory that Claude Code syncs between team members. After a sync across several stores, Claude Code now keeps unsent changes marked as pending while any store is paused after a failure, which is called backing off. It also wakes the sync again once the pause ends. Before, changes stayed pending only after a failure or when sending was held back for another reason.\n\n**Why**\n\nTeam memory changes that are held back during a pause are now sent later rather than lost.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}