{"version":"2.1.281","anchor":"cloud-file-sync-new-install-ack-pass-publishes-an-install","canonical_anchor":"cloud-file-sync-new-install-ack-pass-publishes-an-install","heading":"Cloud file sync: new install_ack pass publishes an install report without uploading","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-file-sync-new-install-ack-pass-publishes-an-install","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud file sync: new `install_ack` pass publishes an install report without uploading\n\nCloud file sync gains an `install_ack` pass that only republishes the install report, without pulling or uploading\n\n**Unclear.** The finding does not say what sets off an `install_ack` pass.\n\n**What**\n\nCloud file sync keeps your machine and a cloud session's copy of the project in step. It works in passes, and each pass is started by a trigger. There is a new trigger, `install_ack`. A pass started this way skips the pull and the snapshot. It only republishes the session note, which is the install report.\n\nIt logs `tengu_dir_sync_git_install_ack` with an outcome or one of these skip reasons:\n\n- `nothing_owed`\n\n- `upload_announced`\n\n- `no_note_yet`\n\n- `peer_behind`\n\nThe fallback message for a failed upload is no longer raised for these passes.\n\n**Why**\n\nThe install report can now be sent on its own, without a full sync. Because these passes do not upload anything, they no longer set off the failed-upload message.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}