{"version":"2.1.248","anchor":"sync-reports-separate-could-not-send-from-unreadable","canonical_anchor":"sync-reports-separate-could-not-send-from-unreadable","heading":"Sync reports separate \"could not send\" from \"unreadable\"","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/sync-reports-separate-could-not-send-from-unreadable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Sync reports separate \"could not send\" from \"unreadable\"\n\nSync failure reporting splits \"could not send\" from genuinely unreadable content.\n\n**What**\n\nSync feature reporting no longer lumps failures under a single \"unavailable\" label. An internal error now reports as `could_not_send`, and a give-up state reports as `unreadable` only when the underlying cause was a read failure, otherwise `could_not_send`.\n\n**Evidence**\n\n`reason: P.gaveUp === \"read_failed\" ? \"unreadable\" : \"could_not_send\"`\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}