{"version":"2.1.242","anchor":"sync-explains-skipped-dependency-folders-and-cloud-container","canonical_anchor":"sync-explains-skipped-dependency-folders-and-cloud-container","heading":"Sync explains skipped dependency folders and cloud container restarts","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/sync-explains-skipped-dependency-folders-and-cloud-container","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Sync explains skipped dependency folders and cloud container restarts\n\nSync tells you when vendor or node_modules files are skipped, and pauses if the cloud side restarts.\n\n**What**\n\nPer-file sync now tells you when tracked files under directories like `vendor\/`, `build\/` or `node_modules\/` are being left out for the session, and it recognises when the cloud side has stopped: if that container is restarted and loses track of which files were synced, sync halts with a message saying so, and resumes when the peer comes back.\n\n**Details**\n\n- Two reasons are given for leaving a dependency directory out: it holds more files than a single turn can track, or those files are not checked out on this machine.\n- The halted-peer state and the dependency-exclusion reporting are both new; neither exists in v2.1.241.\n\n**Evidence**\n\n`its container was restarted and lost track of your synced files`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}