Who is down right now

26 down now · 292 this week

dbt Labs · Data and observabilityNov 14, 2026, 06:58 UTC 8 days ago

Update to spark-utils package causing job run failures

MinorNot disclosedUpdated 7d ago
Nov 14, 06:58 UTCNov 14, 07:56 UTC
Duration
58m
Impact
Minor
Root cause
Not disclosed
dbt Labs, 90 days
40 incidents
Affected
Not listed by the vendor.
Status page

Final update

The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.

Timeline

  1. Resolved · Nov 14, 07:56 UTC
    The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.
  2. Monitoring · Nov 14, 07:30 UTC
    We have released a fix for the issue with the spark-utils package. Version 0.3.5 is now available on the dbt Hub and restores the previous working behaviour. Projects that resolve the latest version of spark-utils will pick up 0.3.5 automatically on their next run, and no action is required. If your `package-lock.yml` was updated to spark-utils 0.3.4, run `dbt deps --upgrade` to update it, or pin spark-utils to 0.3.5. We are continuing to monitor. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues.
  3. Identified · Nov 14, 06:58 UTC
    We have identified an issue with a new release (`0.3.4`) of the dbt package `spark-utils`. Jobs fail with the following compilation error: `In dispatch: No macro named 'assert_not_null' found within namespace: 'dbt'` This affects projects that depend on `spark-utils`, either directly or through another package (for example, Fivetran source packages), on adapters other than Databricks/Spark. Projects that use a `package-lock` file are not affected unless the lock file was updated after the new release. As a workaround, pin `spark-utils` to version `0.3.3` in your `packages.yml`, then run `dbt deps`. We are working on a fix to resolve the issue and will provide an update as soon as it is available. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues.

More from dbt Labs

Full history