You'll notice
Useful3 Signal2
Sync now says in plain words why a file was skipped, including broken settings files.
What's wrong with this entry?
Anonymous. No account, no email.
What
When 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.
Details
- The last case points you at
/status: "a settings file has errors, so your Read rules are unknown (see /status)". - 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.
- The push side gained a matching count of tracked credential files that were withheld.
Evidence
a settings file has errors, so your Read rules are unknown (see /status), dir_sync_worker_pull_credential_refused
Strings lifted out of the shipped bundle, so the claim above can be checked against them.