{"version":"2.1.288","anchor":"team-memory-pull-now-reports-partial-failures","canonical_anchor":"team-memory-pull-now-reports-partial-failures","heading":"Shared team memory sync now reports which files failed and retries them","tier":"notice","area":"Elsewhere","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/team-memory-pull-now-reports-partial-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Shared team memory sync now reports which files failed and retries them\n\nWhen pulling shared team memory partly fails, Claude Code now logs how many files failed and keeps them queued for the next sync\n\n**What**\n\nTeam memory is notes shared across a team that Claude Code downloads and keeps in step with a local copy. When pulling it from several stores partly fails, Claude Code now:\n\n- logs how many downloads failed and how many local removals failed\n\n- leaves its sync record unchanged for those files, so a later sync tries them again\n\n- reports the number of failed downloads\n\nFailed files are no longer silently dropped from the sync record. Previously only the first error was kept and no counts were logged. A successful pull also reports a little more about entries it handled.\n\n**Why**\n\nFiles that fail to sync are no longer quietly lost, and the logs show how much went wrong, which makes sync problems easier to spot.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}