{"version":"2.1.242","anchor":"directory-sync-path-checks-moved-onto-the-storage-backend","canonical_anchor":"directory-sync-path-checks-moved-onto-the-storage-backend","heading":"Directory-sync path checks moved onto the storage backend","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/directory-sync-path-checks-moved-onto-the-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Directory-sync path checks moved onto the storage backend\n\nPath checks for directory sync go through the storage backend, and the mismatch warning wording is shared.\n\n**What**\n\nChecks on paths owned by directory sync now classify a path as real, absent, redirected or not-a-directory through the storage backend when that backend is active, falling back to walking the path with lstat otherwise. The message you see when a session's sync was set up from a different directory now comes from a single shared helper on both paths.\n\n**Details**\n\n- Probe failures now have distinct codes, and a classifier for a vanished source produces codes such as `batch_dir_vanished` and `source_unverifiable_parent_link`.\n- Whether the backend path or the lstat fallback runs is decided by an internal storage-backend check that is not named in the surrounding code.\n\n**Evidence**\n\n`sync-owned path probe: unexpected answer`\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}