Skip to main content

Scheduled Deployments and Quick Deploy

A deployment does not have to run the moment it is ready. mtdt.io separates the two expensive steps — validate (compile and run tests) and deploy (commit the change) — so the slow one can happen during the day and the risky one during a release window.

Quick Deploy​

A validation is a check-only run: Salesforce compiles the package and runs the tests without committing anything. If it passes, Salesforce keeps the result for 10 days and lets you commit that exact package without recompiling or re-running tests. That second step is Quick Deploy, and it takes seconds instead of the full test run.

In mtdt.io:

  1. Run Validate on the deployment.
  2. When it passes, the run in Deploy History offers Quick Deploy.
  3. Quick Deploy carries the configuration the validation ran with. A validation from a different deployment, or one that no longer matches the package, is refused rather than silently deployed.

After 10 days Salesforce discards the validation and the package has to be validated again.

Scheduling​

Both a validation and a quick deploy can be scheduled instead of run now.

  • The picker works in quarter-hour slots — the run starts at the selected quarter hour.
  • A scheduled quick deploy can be placed no later than 10 days after its validation; the dialog shows the exact latest slot.
  • A scheduled run shows its planned time in the deployment header until it starts.
  • Cancel removes a schedule that has not fired. A run that already started is not affected by cancelling the schedule — it continues and finishes.

Approvers can schedule from the approval screen as well, so an approved deployment runs in the release window unattended.

Which one to use​

  • Deploy now — small changes, sandboxes.
  • Validate now, Quick Deploy later — production releases, where you want the tests out of the way before the window opens.
  • Scheduled validation — large packages you want validated overnight against a busy org.

Approvals apply to scheduled runs exactly as they do to immediate ones. See Deployment Approvals.