
dbt State: lag_tolerance is now a budget decision
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…
The skinny
The skinny isn't ready yet — notes appear once the transcript is processed.