{"version":"2.1.248","anchor":"file-refusals-say-whether-they-are-worth-retrying","canonical_anchor":"file-refusals-say-whether-they-are-worth-retrying","heading":"File refusals say whether they are worth retrying","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/file-refusals-say-whether-they-are-worth-retrying","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### File refusals say whether they are worth retrying\n\nSkipped files during sync now record whether the cause was momentary and worth retrying.\n\n**What**\n\nWhen a file is skipped during a sync, the result now records whether the cause was momentary. Transient causes (the file changed while being read, an unrecognised system error) are marked retryable; structural ones (not a regular file, resolved outside its directory) are not.\n\n**Evidence**\n\n`why: \"resolved outside its directory\"`\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}