{"version":"2.1.219","anchor":"team-memory-mounts-can-un-suppress-themselves","canonical_anchor":"team-memory-mounts-can-un-suppress-themselves","heading":"Team memory mounts can un-suppress themselves","tier":"notice","area":"Org Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/team-memory-mounts-can-un-suppress-themselves","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Team memory mounts can un-suppress themselves\n\nA memory mount that got suppressed can now recover on the next sync instead of staying stuck until restart.\n\n**What**\n\nTwo suppression reasons on multi-store memory sync are now recoverable instead of sticking until restart.\n\n**Details**\n\n- Applies to `mount_dir_foreign_partition` and `mount_dir_unmanifested_nonempty`\n- On the next sync the mount dir is re-examined; if the partition now matches or the dir is empty, suppression is cleared with the log \"condition cleared \u2014 re-adopting the mount dir\" and failure counters reset\n- In the same area the separate `pushSuppressedReason` field is gone entirely, so pushes and periodic resync are no longer gated on it and per-mount suppression is the single mechanism\n- Gating of team memory sync itself was not examined\n\n**Evidence**\n\n`condition cleared \u2014 re-adopting the mount dir`\n\n- Area: Org Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}