dbt Labs: dbt Wizard SQL execution failing
Affected components: 01JBCBN121Z1F9B5FAMH1S60Q201JBCBN2A6VZMT4ZRW91WN0NYE01JBCBN3K5MXCY240R6W6ZXBDN01JBCBN62ETXP6QRK5J6YNG35G01JBCD30K9E60W477WMVG7TACX01JBCQT95MMQW28YZWSEP9948N01JBCQXMV657YMBPAER8P6K1J801JBCR295NGTH0QAJTVCSEX9XC01JH8R89TP17P9XAV1D761QJ8M01JRKCJTBRSS3842ZKCX42E0C601K1EH8NN4D80QNPDKGJPTD6FP01K4T29F32XVJP50X5W35G5BA601KF46A8MACZNFTCSK3D3AK1A101KSMXDZME8P7GTPC0JKZ0RN4S01KX12QA4B240QR71GYGGZ7CF2
Timeline of updates
- investigatingEdited
We’re investigating an issue with dbt Wizard that is causing requests that run SQL or Semantic Layer queries to fail with an error. This is impacting dbt Wizard in all multi-tenant regions anytime after 16:32 UTC (12:32 PM Eastern Time). The team is working on a resolution and we will provide updates as soon as new information becomes available.
dbt platform jobs, and the Studio IDE are not impacted and should be running as expected.
- identified
We have identified an issue with dbt Wizard that resulted in failed parsing of semantic layer's QueryResult response. A fix is being implemented, and we will provide an update shortly.
- monitoring
We have deployed a fix for dbt wizard that was causing failed parsing of semantic layer's QueryResult response. dbt Wizard has returned to its normal state and we are continuing to monitor.
- resolved
The issue has been resolved, and all affected systems are now functioning normally as of 5:50pm UTC.
Please contact Support via email support@getdbt.com: http://support@getdbt.com (opens in new tab) if you continue to experience delays and are unsure of the root cause.
Changes Rewindex caught on this incident
- Major incident: dbt Wizard SQL execution failing
- Incident updated: dbt Wizard SQL execution failing
- Incident updated: dbt Wizard SQL execution failing
- Incident silently edited: dbt Wizard SQL execution failing
- Incident updated: dbt Wizard SQL execution failing
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.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.getdbt.com (opens in new tab).