{"version":"2.1.246","anchor":"files-too-large-to-sync-are-now-called-out-by-name","canonical_anchor":"files-too-large-to-sync-are-now-called-out-by-name","heading":"Files too large to sync are now called out by name","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/files-too-large-to-sync-are-now-called-out-by-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Files too large to sync are now called out by name\n\nFiles skipped by cloud sync for being too large are now named, up to five paths.\n\n**What**\n\nCloud directory sync now warns when individual files are skipped for being over the size limit, naming up to five paths, instead of dropping them silently. The size limit is filled in at runtime.\n\n**Details**\n\n- Oversize files are tracked in their own bucket, separate from the other reasons a file is held back.\n- The message ends with the fragment `MiB each), so changes to them stay on this machine: `.\n- Related: the internal \"uploads not taken\" lines dropped from info level to debug, so they no longer appear in the normal log stream.\n\n**Evidence**\n\n`MiB each), so changes to them stay on this machine: `\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}