{"version":"2.1.199","anchor":"memory-sync-richer-status-messages-and-auto-retry","canonical_anchor":"memory-sync-richer-status-messages-and-auto-retry","heading":"Memory Sync: Richer Status Messages and Auto-Retry","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.199\/e\/memory-sync-richer-status-messages-and-auto-retry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.199","markdown":"### Memory Sync: Richer Status Messages and Auto-Retry\n\nMemory sync status messages now communicate more precisely why a sync is paused and whether it will self-recover.\n\n**Details**\n\n- Distinguishes transient pauses (\"sync retries automatically and will push it once the server recovers\") from permanent suppression (\"NOT being synced to shared\/server memory\")\n- `suppressedUntilMs` field allows sync to schedule automatic retry after transient failures\n- New concurrent write conflict recovery: when another session updates a memory file while a write is in flight, the local write is reloaded from the server's version and the author is notified to re-apply their change\n- `mount_dir_foreign_partition` error gives a specific message explaining split-store conflict\n\n**Evidence**\n\n(search for `\"Memory sync is currently paused\"`, `\"sync retries automatically\"`, `\"concurrent-write conflict\"`)"}