Render Issues when trying to send looks including viusualizations to Slack
See original GitHub issueWhen trying to schedule or send a look to lookerbot containing visualizations I get the error message “⚠️ An error has occurred.” in Slack. Sending looks without visualizations works fine. I run a self-hosted Instance of looker.
The error I receive in the looker.log, when sending a look containing a visualization is the following:
StandardError` : Render job 5e448255f095a2a04279091ff588fc0c[5882] failed ["Unexpected document content"]
The lookerbot documentation said the format selection for the output sent to the webhook would be ignored. However when I analysed the traffic sent to lookerbot, I saw that the content sent to lookerbot ss always the format selection I chose, when scheduling the look. For example CSV, html and so on.
I did set environment variables for a google cloud bucket. However the error appears regardless of these variables being set.
I have tried to give the bot user all different kind of rights in looker and tested all options through sudoing as the bot user. This should not be related to looker rights.
I am currently running looker Version 5.16.18
Can someone help me with this or at least tell me which format looker should use to send data containing a visualization to lookerbot?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top GitHub Comments
I think the documentation is still correct – due to limitations in how data could be sent at the time Lookerbot actually runs the query twice.
It looks like an error on Looker’s end, I’ll do some investigation internally.
I think I realized what is going on. I think something changed about labs features and the documentation. If I recall correctly the documentation used to say
Now it is:
Furthermore an option I was looking for, for the longest time, in Labs features appeared with the latest version called
Enhanced Rendering
. Even though the documentation always linked to this option, for what I was trying to achieve. it never showed up on my on-premise-Instance. When I try to activate it now, however it gives the following output:Chromium 65 or above must be installed on the server to enable this feature.
I assume this option never showed up before, because I did not have Chromium installed on the machine. Sadly my looker-Instance is running on Debian8 and I cannot install Chromium 65 on it, because of that for now.
On another note a further documentation page is now available, or at least I did not ever find it before. It is the following: https://docs.looker.com/setup-and-management/on-prem-install/on-prem-labs
It lists the necessity of Chromium 65.
Even though my problem is not gone, I know why it won’t work through the added documentation.
most likely solution: Update to Debian 9.
I guess this Issue can be closed.