{"version":"2.1.223","anchor":"notice-when-a-memory-file-is-too-large-to-sync","canonical_anchor":"notice-when-a-memory-file-is-too-large-to-sync","heading":"Notice when a memory file is too large to sync","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/notice-when-a-memory-file-is-too-large-to-sync","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Notice when a memory file is too large to sync\n\nYou get told once when a memory file is too big to sync and may be lost.\n\n**What**\n\nFiles inside a synced memory mount that exceed the per-file limit produce a notice saying the file is saved locally but not synced, that its changes will be lost when the machine is recycled, and instructing that the user be told.\n\n**Details**\n\n- Emitted once per path, tracked per mount directory, so it does not repeat.\n- Whether this path is reachable for everyone in this build could not be resolved; there is no gate on it.\n\n**Evidence**\n\n`per-file sync limit`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}