{"version":"2.1.248","anchor":"directory-sync-seeding-reports-a-settled-outcome","canonical_anchor":"directory-sync-seeding-reports-a-settled-outcome","heading":"Directory sync seeding reports a settled outcome","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/directory-sync-seeding-reports-a-settled-outcome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Directory sync seeding reports a settled outcome\n\nThe first copy of your directory to the cloud now reports a settled outcome and whether the first pass finished.\n\n**What**\n\nThe initial copy of your directory to the cloud now reports one of three end states (`off`, `left`, `running`) plus whether the first full pass completed, and that flag is sent as `first_pass_done` in the seed telemetry.\n\n**Details**\n\n- Stopping because the session shut down is now distinguished from other stop reasons.\n- The exit-time cutoff became a three-way state check covering started, cut and done rather than a single either\/or.\n\n**Evidence**\n\n`b(\"ccr_dir_sync_seed\", { git_engine: !0, first_pass_done: qe })`\n\n- Area: Directory Sync\n- Names: `first_pass_done`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}