Skip to main content
September 30, 2026
Private preview. Paradime State is in private preview. To get early access for your workspace, reach out to the Paradime team at support@paradime.io.
A Paradime State run summary for dbt build: 78 nodes executed, 46 skipped, 29 rejudged, and an estimated 14.2 minutes of compute saved
Paradime State now covers more of your project, and it steps aside safely when it can’t help.
  • dbt snapshot is state-aware. Each snapshot is decided the way it already was inside dbt build, so an unchanged snapshot can be skipped instead of always running. dbt seed and dbt test on their own still run as plain dbt™.
  • dbt build --full-refresh works. It used to fail when the build included snapshots or tests. Snapshots still run, and keep their history. --resource-type and --exclude-resource-type on dbt build also work, and choose which steps run.
  • Snapshots run after the models they read. In a dbt build, a snapshot that reads a model rebuilt in the same build now runs with the models, so it captures the new version of the data. A first build into an empty schema no longer fails on a table that doesn’t exist yet.
  • A compile error no longer fails the run. If your project can’t be compiled for Paradime State, the command runs as plain dbt™, and the summary says that State stood aside and why.
  • A summary you can trust. executed counts only what dbt™ reported as built, and a new not built line lists anything a failed step didn’t build.
  • Faster on Snowflake. The check for changed source data sends one metadata query per database instead of one per schema.
The first state-aware run after this update runs every data test once, because tests are now compared by their definition rather than their compiled SQL. See Read a run and Troubleshooting. Shipped in Paradime v6.17.0.