3 weeks ago
Queries that previously worked started failing in SQL Warehouse (Dashboards) without any changes on our side.
The query succeeds, but fails to render results with error:
"Cannot read properties of undefined (reading 'data')"
This happens with:
- system.billing.usage (when selecting struct fields like identity_metadata.run_as)
- queries with aggregations and joins (even after fixing GROUP BY consistency)
The same query works:
- in notebooks
- when simplified
But fails:
- in SQL Warehouse (dashboard/editor)
This indicates a regression in result rendering or query execution plan.
Example query:
Error: The query succeeded, but we are unable to display the results due to the following error that occurred while fetching the data: Cannot read properties of undefined (reading 'data').
This same problem is repeated in the Dashboard you suggested in the link https://github.com/databricks/tmm/blob/main/System-Tables-Demo/Lakeflow/LakeFlow%20System%20Tables%2... in the [Operational Observability] Highest Failure Jobs view.
3 weeks ago
Worked until last Friday, no changes in query.
3 weeks ago
Hi,
Just had a look at this and I'm trying to replicate my end, can you confirm what type of compute you're using? And is it the SQL editor that it's failing in? Also what region and cloud you're using?
I ran the cost query on serverless and it ran fine for me, so want to be able to replicate. I'm also trying to work out if it's a know issue.
Thanks,
Emma
3 weeks ago
Hi Emma!
I'm using a serverless SQL Warehouse, and yes, the error occurs in the Dashboard editor. We are in the us-east1 region.
The error was: "The query succeeded, but we are unable to display the results due to the following error that occurred while fetching the data: Cannot read properties of undefined (reading 'data')."
A little before 12 PM, Sรฃo Paulo, Brazil time, I ran the query and the problem didn't recur. I don't know if there was a fix or update, but it reflected and the behavior no longer exists.
Thursday
Hello Emma,
The behavior has started happening again.
Thursday - last edited Thursday
2 weeks ago
Same problem here. I have previously reported this issue, and it had been resolved at the time. However, the problem has now reoccurred.
When ingesting large tables (over 100k rows), the system is unable to properly render the data, preventing the tables from being displayed.
