{"version":"2.1.248","anchor":"file-sync-refusal-for-large-checkouts-is-now-stated-purely-a","canonical_anchor":"file-sync-refusal-for-large-checkouts-is-now-stated-purely-a","heading":"File sync refusal for large checkouts is now stated purely as a size","tier":"notice","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/file-sync-refusal-for-large-checkouts-is-now-stated-purely-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### File sync refusal for large checkouts is now stated purely as a size\n\nFile sync now refuses large checkouts purely on byte size, not untracked file count.\n\n**What**\n\nWhen a cloud session declines to offer file sync because your checkout has too much uncommitted content, the reason is now always a byte size compared against a fixed limit, replacing an earlier three-way check that could also refuse for having too many untracked files.\n\n**Details**\n\n- The single reason reported is `untracked_too_large`, and the user-facing line always cites a size.\n\n**Evidence**\n\n`File sync is not offered for this checkout:`\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}