{"version":"2.1.227","anchor":"teammate-mailboxes-and-team-files-move-to-the-newer-storage-","canonical_anchor":"teammate-mailboxes-and-team-files-move-to-the-newer-storage-","heading":"Teammate mailboxes and team files move to the newer storage backend","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/teammate-mailboxes-and-team-files-move-to-the-newer-storage-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Teammate mailboxes and team files move to the newer storage backend\n\nTeammate mailbox and team-config writes use the newer storage layer when it's present.\n\n**What**\n\nMailbox writes, marking messages read, message pruning and team-config updates now go through a transactional storage update when the session has the newer storage backend, and fall back to the old lockfile-plus-atomic-write path when it does not.\n\n**Details**\n\n- The new path retries when a lock looks suspect and separates contention from hard failures in telemetry.\n- Hard failures surface as \"Team file update failed (storage v5)\".\n- The old file-based mailbox read and clear helpers are gone.\n\n**Evidence**\n\n`Team file update failed (storage v5)`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}