{"version":"2.1.281","anchor":"dir-sync-first-send-waits-behind-another-writers-lock-and-r","canonical_anchor":"dir-sync-first-send-waits-behind-another-writers-lock-and-r","heading":"Dir-sync first send waits behind another writer's lock and records more detail","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/dir-sync-first-send-waits-behind-another-writers-lock-and-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Dir-sync first send waits behind another writer's lock and records more detail\n\nDirectory sync's first send now waits for another writer's lock to clear instead of failing, and reports more detail\n\n**What**\n\nWhen directory sync (the feature that copies your files through git) sends for the first time, it may find that another process on the same machine holds a lock, meaning that process is writing. Before, this counted as a failure. Now sync waits for the lock to clear. If the writer is on a different machine, sync stops waiting. Other changes:\n\n- The step that captures the current state can now report `kept_here` with reasons such as `local_failures`, or `failed` with `uploads_failing`.\n\n- The usage event `tengu_dir_sync_git_capture_point` gains a reason field, and the first-send data records `writer_elsewhere` and `lock_waited`.\n\n- A new `install_ack` trigger sends an update after incoming changes are applied.\n\n- The stopped state now reports whether the first upload happened.\n\n- Some waiting messages were reworded, for example \"your message goes as soon as that clears.\"\n\n**Why**\n\nA second process writing to the same folder should no longer make the first sync fail. Instead, your message is sent as soon as the other process finishes.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}