{"version":"2.1.238","anchor":"sync-now-explains-in-plain-words-why-a-file-was-skipped","canonical_anchor":"sync-now-explains-in-plain-words-why-a-file-was-skipped","heading":"Sync now explains in plain words why a file was skipped","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/sync-now-explains-in-plain-words-why-a-file-was-skipped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Sync now explains in plain words why a file was skipped\n\nSync now says in plain words why a file was skipped, including broken settings files.\n\n**What**\n\nWhen directory sync leaves a file behind, it now assembles a sentence from a fixed set of reasons: the file is sensitive, it is sensitive but tracked by git, reading it was denied, or your Read rules could not be determined because a settings file has errors.\n\n**Details**\n\n- The last case points you at `\/status`: \"a settings file has errors, so your Read rules are unknown (see \/status)\".\n- On the pull side, rows whose path looks like a credential are marked refused rather than written to disk, counted, and raised as a warning-level event.\n- The push side gained a matching count of tracked credential files that were withheld.\n\n**Evidence**\n\n`a settings file has errors, so your Read rules are unknown (see \/status)`, `dir_sync_worker_pull_credential_refused`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}