{"version":"2.1.229","anchor":"adopted-agent-and-file-sync-failures-carry-codes","canonical_anchor":"adopted-agent-and-file-sync-failures-carry-codes","heading":"Adopted-agent and file-sync failures carry codes","tier":"internal","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/adopted-agent-and-file-sync-failures-carry-codes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Adopted-agent and file-sync failures carry codes\n\nAgent adoption and file-sync failures now come with specific reason codes instead of just a message.\n\n**What**\n\nValidation failures when adopting an agent now come with codes such as `ADOPT_WRONG_LEAF`, `ADOPT_PARENT_NOT_REGULAR` and `ADOPT_SCOPING_UNUSABLE`, and file-sync status lines pair their message with a reason: `lane_full`, `too_many_files`, `store_unreadable` or `seed_incomplete`.\n\n**Evidence**\n\n`ADOPT_SCOPING_MISMATCH`\n\n- Area: File Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}