Prerequisites
- A scheduler connection to your warehouse.
- An existing Bolt schedule.
- Defer to production enabled on that schedule.
How it works
With defer on, dbt™ resolves aref() from the production manifest when the referenced model is both not in the current run’s selection and not present in your development schema. Paradime fetches the latest manifest.json automatically, so you always defer against current production state.
Steps
1
Open the defer menu
In the editor toolbar, next to the run button, open the defer menu.
2
Choose a defer mode
- Standard defer to production: reads production objects only when needed.
- Defer with
--favor-state: always reads from the production manifest, even when the model exists in your development schema.
Compiled SQL now references your production schema for unchanged parents. Compare a deferred run with a standard one:The deferred run reads
- Deferred (production schema)
- Standard (development schema)
dbt_prod; the standard run reads your dev schema. After a deferred run, the Terminal prints a clickable link to the Bolt run it deferred against.Review dbt’s state comparison caveats to understand the limitations.
Next steps
Schedule settings reference
Enable defer to production on a Bolt schedule.
Create a Bolt schedule
Set up the production run defer relies on.