Episode Details
Back to Episodesdbt State: lag_tolerance is now a budget decision
Description
dbt State went generally available in September 2026, so rebuilding every model on a cron schedule is now a choice rather than a default. The position here: the tool cannot tell you how stale each model is allowed to be, and the lag_tolerance config most teams set once and globally is a business decision about decision cadence, not an engineering setting.
You leave with a method: meter wasted rebuilds using BigQuery INFORMATION_SCHEMA.JOBS or Snowflake credit consumption, tie tolerance to the decision each model feeds, keep source freshness checks running, read the Explain tab in audit mode, and cap agent queries with resource monitors and maximumBytesBilled. Includes the RxBenefits 59% result, dbt's 15 to 30% range, FinOps Foundation and Flexera 2026 findings.
Key takeaways
- Calculate last month's share of scheduled runs that rebuilt models whose upstream sources had not changed, and treat that number as your addressable budget.
- Set lag_tolerance per model to the cadence of the decision it feeds, never shorter, and flag models where nobody can name the decision.
- Keep source freshness checks on their own schedule, because reused models skip their tests and silent semantic drift passes volume checks.
- Run dbt State on one non-critical job with conservative tolerances and read the Explain tab for a week before trusting it widely.
- Set Snowflake resource monitors with suspend triggers and BigQuery maximumBytesBilled so agent-generated queries cannot run up an overnight surprise.
Chapters
0:00 Why 60% of scheduled model builds repeat
1:13 What dbt State GA actually changes
2:57 Metering wasted rebuilds before flipping the switch
4:18 Silent semantic drift when models are reused
5:41 Committed spend contracts hide the savings
6:57 Capping autonomous agents in the warehouse
Go deeper, free lessons
- Data FinOps: controlling cloud data cost
- dbt (data build tool): industrialized SQL transformation
- Performance & scalability: partitioning, clustering & cost optimization
- Cloud data infrastructure: services, costs & migration
- Chargeback & showback models
The article: https://www.mba-training.com/en/blog/cloud-data-costs-dbt-state
MBA Training, mba-training.com