{"version":"2.1.251","anchor":"background-file-sync-now-steps-aside-for-commands-in-flight","canonical_anchor":"background-file-sync-now-steps-aside-for-commands-in-flight","heading":"Background file sync now steps aside for commands in flight","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/background-file-sync-now-steps-aside-for-commands-in-flight","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Background file sync now steps aside for commands in flight\n\nBackground file sync now skips itself while a sync-sensitive command is running.\n\n**What**\n\nThe background pass that syncs your working directory to a cloud session now runs as a distinct \"watch\" pass. When a command that is sensitive to syncing is already running, the watch pass is skipped rather than run, and it tells you sync keeps trying at each sync point instead of using the message-blocking wording reserved for foreground sends.\n\n**Details**\n\n- The skip is recorded with the reason `held_for_command`.\n- Foreground triggers (sending a message, creating or capturing a session) are unaffected and still run their pass immediately.\n- The trigger type is set internally by whichever code path starts the pass; there is no setting for it.\n\n**Evidence**\n\n`held_for_command`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}