{"version":"2.1.248","anchor":"clearer-wording-when-a-peer-machine-cannot-catch-up-on-synce","canonical_anchor":"clearer-wording-when-a-peer-machine-cannot-catch-up-on-synce","heading":"Clearer wording when a peer machine cannot catch up on synced files","tier":"notice","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/clearer-wording-when-a-peer-machine-cannot-catch-up-on-synce","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Clearer wording when a peer machine cannot catch up on synced files\n\nFile sync now explains in plain words why a command was held and what would clear it.\n\n**What**\n\nFile sync across machines now explains, in plain language, each reason a command was held or deferred and what clears it: the branch changed, capped until upload finishes, an upload-only device, files still arriving, the peer is serving another command, sync stopped there, or the other side's engine is too old to sync mid-turn. Read-only tool calls are never held; they run and carry a note instead.\n\n**Details**\n\n- Each message pairs a cause with a remedy rather than just refusing.\n- The oldest-engine case tells you the command ran against that machine's files as of the user's last message, so your recent edits may be missing.\n\n**Evidence**\n\n`syncs this session's files only at turn boundaries (its sync engine has no mid-turn sync points); the command ran on that machine's files as of the user's last message, which may not include your edits here`\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}