{"version":"2.1.281","anchor":"cloud-file-sync-a-warning-and-telemetry-when-cloud-changes","canonical_anchor":"cloud-file-sync-a-warning-and-telemetry-when-cloud-changes","heading":"Cloud file sync: a warning and telemetry when cloud changes keep being refused","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-file-sync-a-warning-and-telemetry-when-cloud-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud file sync: a warning and telemetry when cloud changes keep being refused\n\nCloud file sync now tracks repeated refusals of cloud changes, warns if they persist and says when changes arrive again\n\n**What**\n\nCloud file sync keeps the project on your machine and a cloud session's copy in step. Sometimes changes made in the cloud session are refused on your machine. Those refusals are now counted over turns, where a turn is one exchange between you and Claude:\n\n- A first refusal shows the same short-lived line as before.\n\n- If refusals continue past a set number of turns, a stronger warning is shown. Git errors use their own threshold.\n\n- At that point Claude Code logs `tengu_dir_sync_git_apply_down_lasting_refusal` once, with the turn count and the reason.\n\n- When a sync round succeeds again, you see \"Cloud changes are reaching this machine again\".\n\n- A refusal with the reason `aborted` is now ignored without any message.\n\n**Why**\n\nA refusal that keeps happening now gets a clear warning instead of the same passing line every turn. You are told when changes start coming through again.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}