Slightly unhelpful error message when lookerbot can't access the look.

[kyledemeule]

Recently we had someone setting up a webhook, but they were getting this error message posted in slack instead of the content:
Couldn't parse Looker response. The server may be offline.
The user that our lookerbot API Token didn't have access to the look, so when it tried to request the look I think it was getting a 404 response with an HTML body. I think this code tries to parse it as JSON, which understandably throws an exception which is caught, but has this error message, which isn't obvious that this is a resource not found/permissions issue. An additional response code check for 404 like this could probably deliver an error message that would make it more obvious that it's a permission issue.

[JohnOMDev]

@kyledemeule , do you find a solution. Looker support hasn't be helpful. It 404 error and the user that owns the API secret and Client Id is the Admin.

{ error: "Couldn't parse Looker response. The server may be offline." }

[kyledemeule]

@JohnOMDev sorry no - I no longer use Looker.

[BDuelz]

@kyledemeule , do you find a solution. Looker support hasn't be helpful. It 404 error and the user that owns the API secret and Client Id is the Admin.

{ error: "Couldn't parse Looker response. The server may be offline." }

We're also getting this same error when running lookerbot v0.0.15. Been working on it for weeks now with little progress.

[JohnOMDev]

@BDuelz , any progress? Can you please tell me what you did? I am working with looker support but seems weird that we can't find solution(s) for a month.