Changes dbt Labs dbt deps failures in dbt job runs and Studio

dbt Labs: Incident silently edited: dbt deps failures in dbt job runs and Studio

Silent editWording only (typesafe/jev-1.13-20260917, 67%)Changed 2026-10-22 18:43 UTCstatus.getdbt.com

Summary

The 10-22 11:16 UTC investigating update was recorded as edited, but its text is unchanged: dbt invocation issues were causing dbt deps failures, and the team was working on a resolution. No new customer-impact, duration, cause or fix information was added.

Machine-written from the diff below (Sol; type: incident edit). Check the diff before relying on it.

Incident page: the full timeline of updates

What changed

~~Struck in red~~ is what dbt Labs removed; blue is what they added. Muted text is unchanged context.

ChangedUpdateinvestigating2026-10-22 11:16 UTC#1

~~We're investigating an issue with dbt invocations that is causing dbt deps failures. The team is working on a resolution and we will provide updates as soon as new information becomes available.~~

We're investigating an issue with dbt invocations that is causing dbt deps failures. The team is working on a resolution and we will provide updates as soon as new information becomes available.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Oct 22
Before captured 18:13 UTC
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on Oct 23, 11:49 UTC. Record hash 8bf1398a20242337…
Download proof
Oct 22
After captured 18:43 UTC
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on Oct 23, 11:49 UTC. Record hash 748e5f9f7795de43…
Download proof

History of this incident

Friday, October 23

1 incident change

Normal progress
05:33Incident
Incident updatedbt deps failures in dbt job runs and Studio

Thursday, October 22

3 rewrites, 2 incident changes

Normal progress
23:53Incident
Incident updatedbt deps failures in dbt job runs and Studio
Normal progress
18:53Edited by the vendor
dbt deps failures in dbt job runs and Studio
The identified update at 10-22 13:02 UTC was marked edited, but its text is unchanged: dbt deps was affected in Studio projects and some job runs, and engineering was rolling back a change it believed caused the issue. The edit adds no new customer-impact or resolution information.
Wording only
18:43Edited by the vendor
dbt deps failures in dbt job runs and Studiothis change
The 10-22 11:16 UTC investigating update was recorded as edited, but its text is unchanged: dbt invocation issues were causing dbt deps failures, and the team was working on a resolution. No new customer-impact, duration, cause or fix information was added.
Wording only
18:13Edited by the vendor
dbt deps failures in dbt job runs and Studio
The 10-22 15:58 UTC investigating update was archived with no visible wording change, still describing dbt deps failures affecting dbt invocations. dbt Labs said it was working on a resolution; no impact level, start time, duration, cause, or fix was provided.
Normal progress
17:43Incident
Incident updatedbt deps failures in dbt job runs and Studio

Cite this

Incident silently edited: dbt deps failures in dbt job runs and Studio on dbt Labs’s status page, changed 2026-10-22 18:43 UTC (change 3 of 6).

Title: Incident silently edited: dbt deps failures in dbt job runs and Studio
Vendor: dbt Labs
Date: 2026-10-22 18:43 UTC
URL: https://rewindex.com/change/r67de875bd3ac98

All dbt Labs changes dbt Labs profile Markdown JSON