{"version":"2.1.239","anchor":"a-file-whose-attributes-cannot-be-read-is-now-a-named-sync-o","canonical_anchor":"a-file-whose-attributes-cannot-be-read-is-now-a-named-sync-o","heading":"A file whose attributes cannot be read is now a named sync outcome","tier":"internal","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/a-file-whose-attributes-cannot-be-read-is-now-a-named-sync-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### A file whose attributes cannot be read is now a named sync outcome\n\nFiles whose attributes cannot be read now get a proper named sync outcome instead of an unclassified error.\n\n**What**\n\n`attributes_unreadable` joins the existing sync failure reasons such as lock contention and unreadable peer journals, in the retry decision, the human-readable formatter and the terminal-state classifier, so it is no longer an unclassified error.\n\n**Evidence**\n\n`attributes_unreadable`\n\n- Area: File Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}