Skip to content

Run, Dry Run, and Scan

The job page exposes three distinct execution modes.

Run

Run performs the live operation. This is the mode that consumes data allowance and applies real changes.

Dry Run

Dry Run is the safest first step when you want to understand what the live run would do without performing the transfer.

Use it when you want to review:

  • expected work size
  • likely run duration
  • filter impact
  • whether the job configuration looks safe enough for a live run

Scan

Scan is inventory and analysis focused. It helps you inspect source-side conditions such as naming issues, duplicates, timestamps, and oversized content before a live run.

For a new job:

  1. Dry Run if you want live-run planning
  2. Scan if you want inventory analysis and remediation options
  3. Run when the configuration is ready

See also