Skip to main content
Schedule settings define the schedule’s identity and the Git branch it runs against, plus optional deferral so a run can compare its state against a previous run.

​
Settings

​
Defer to a previous run

Turn on Defer to a previous run to compare state against a previous run instead of building the whole project. This is how you run incrementally: build only the models that changed, refresh only models with newer source data, or re-run from the point of failure. It also powers Continuous Deployment, where a merge deploys only what changed. When the toggle is on, configure:
  • Deferred schedule — the schedule Bolt reads run artifacts from (manifest.json, run_results.json, and sources.json) to work out what changed.
  • Last run type (for comparison) — which run of the deferred schedule to compare against:
    • Last run — the most recent run.
    • Last successful run — the last run that passed, skipping incomplete or failed runs.
Tip: Use Last run unless you are retrying builds, in which case Last successful run avoids comparing against a broken state.
Turbo CI schedules always defer, since they build only the models changed in a pull request. See Triggers and Turbo CI.
Next, set up Self-healing to automatically recover from failed runs.

Define this as code

Set name, description, owner_email, and git_branch in the base config, and deferred_schedule for deferral.

Related topics

Test Code Changes On Pull RequestsRe-executes the last dbt™ command from the point of failureSnapshot Source Data FreshnessRun and Test all your dbt™ ModelsTurbo CI Schema Cleanup macro for dbt™