{"version":"2.1.232","anchor":"two-new-reasons-a-cloud-directory-sync-can-be-refused","canonical_anchor":"two-new-reasons-a-cloud-directory-sync-can-be-refused","heading":"Two new reasons a cloud directory sync can be refused","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/two-new-reasons-a-cloud-directory-sync-can-be-refused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Two new reasons a cloud directory sync can be refused\n\nCloud directory sync now reports unlistable git trees and too-many-files separately.\n\n**What**\n\nDirectory sync now reports `tree_unlistable` when the git tree cannot be listed or the remote ref shas fail validation, and `tree_too_many_files` when the eligible file count exceeds the budget.\n\n**Details**\n\n- Both are terminal reasons recorded in the `ccr_dir_sync_push` telemetry alongside the existing `too_many_files` and `listing_failed`.\n- Both are handled the same way as `too_many_files` by the code that decides what to do after a refused push.\n\n**Evidence**\n\n`tree_too_many_files`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}