{"version":"2.1.248","anchor":"sync-warnings-now-fire-at-most-once-per-run","canonical_anchor":"sync-warnings-now-fire-at-most-once-per-run","heading":"Sync warnings now fire at most once per run","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/sync-warnings-now-fire-at-most-once-per-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Sync warnings now fire at most once per run\n\nTwo sync warnings now appear once per run instead of repeating on every attempt.\n\n**What**\n\nThe cloud-sync session registry gained one-shot latches so the \"git is not on the start path\" and \"unknown engine\" warnings each appear once per process rather than repeating on every attempt.\n\n**Details**\n\n- A lookup for fetching an already-held sync object was added alongside them.\n\n**Evidence**\n\n`sayGitNotOnStartPath`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}