When attempting to download a Looker UI Dashboard in any format, the Looker download browser window is getting stuck in "Queued for Rendering" process.
This happens since we upgraded to the new looker version 23.16.44, we previosouly had and older version 21.xx and had never experienced this issue.
Note: Have seen this other community question https://www.googlecloudcommunity.com/gc/Technical-Tips-Tricks/Render-error-WebSocket-connection-is-n... but this doesn't seem to be the same problem, in my case it is not intermittent, and it has not solved by increasing the chrome/looker memory allocation.
We have contacted looker support but have not been given a solution yet, was wondering if anyone experienced this error in the past and how it got solved. Any thoughts?
Thanks,
Armen
Did you ever find a solution for this? I am running into the same issue.
Did you find a solution to this? I am getting the same error.
I see this problem on our instance on 24.20.39
Every lookml dashboard gets stuck in the 'enqueued_for_rendering' status, but all UDD dashboards render fine after a second or two.
This bug is preventing us from testing a very large amount of dashboards after migrations.
Is this an on-premise instance of Looker, or one hosted by Google?
Just a quick thing to check - Looker, on default settings, can only render two visualizations simultaneously. This is usually fine, unless there is a couple of very long-running queries that are waiting for rendering. So if you see a long-running 'Queued for Rendering' page, go to the Queries Admin Panel and check for long-running queries. This can help identify when PNG or PDF downloads, which may be long-running, are simply waiting for something else to finish.
If you don't see anything there, then the best thing to do is probably to reach out to the Support team.
It is a google hosted instance.
In the end it appears there were a couple of queries stuck running forever, I am not sure why that caused lookml dashboards to fail but not regular ones. I ended up adding a timeout to my process waiting for the render result that simply clears all render queries running on the instance, I do not know if there is a way to know which queries specifically are started by each render task.