@sam8 are you able to confirm if this has been resolved? It appears that it has (things are loading that were not loading earlier). Would be good to know if it’s likely to stay that way, though.
We have identified and pushed the fix. Here’s what I can share from the official report:
First impact period was between 2025-05-05 06:25am and 11:30am US/Pacific. This impact was caused by a bug in the recent Looker Studio version. The issue impacted all types of queries - Bigquery, Looker, Ads and caused around 15% of data query failures. Our engineers identified the bug and applied a fix thereby resolving the first issue at 11:30am US/Pacific. The second impact period was between 2025-05-05 12:20pm and 1:30pm US/Pacific, This impact was due to a previously misconfigured data query server which did not surface earlier. This impacted connectors for Looker, Google Sheets, MySQL and other JDBC connectors. The second failure was addressed at 1:40pm US/Pacific by redirecting the query traffic away from the misconfigured server. |
|---|
The impacted customers would have observed: - Looker Studio has detected a System Error - Slowed data load in their Looker Studio report UI - Dataset configuration error - Looker Studio cannot connect to a dataset. - Trouble loading data on reports error while running the reports. |
yes, this has been fixed! Adding more details in a top-level reply on this post.
1 Like