dbt Cloud incident

[EMEA AWS] Failed or broken AI responses in Copilot

Minor Resolved View vendor source →

dbt Cloud experienced a minor incident on April 13, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2026, 06:50 PM UTC
Resolved
Apr 13, 2026, 06:50 PM UTC
Duration
—
Detected by Pingoru
Apr 13, 2026, 06:50 PM UTC

Update timeline

  1. identified Apr 13, 2026, 03:50 PM UTC

    Status: Identified Beginning 3:50pm UTC some users saw errors when using AI features in dbt Platform (dbt Copilot in Studio), and affected interactions did not complete as expected. The issue was caused by an issue with how our AI service handled cancelled requests, which could leave conversations in an invalid state. Affected components Admin API (EMEA AWS) (Operational) dbt Copilot (EMEA AWS) (Degraded performance) Semantic Layer (EMEA AWS) (Operational) Metadata Ingestion (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational) IDE (EMEA AWS) (Operational) Metadata API (EMEA AWS) (Operational)

  2. resolved Apr 13, 2026, 06:50 PM UTC

    Status: Resolved On April 13, 2026 we deployed a fix to correct this behavior and improved our validation to prevent similar errors going forward. Affected components Metadata API (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational) dbt Copilot (EMEA AWS) (Operational) Metadata Ingestion (EMEA AWS) (Operational) IDE (EMEA AWS) (Operational) Semantic Layer (EMEA AWS) (Operational) Admin API (EMEA AWS) (Operational)