View the original community article here
Last Tested: Mar 11, 2021
Possible Reasons:
- Missing
|
before derived table sql statement for old LookML - There is a non-supported character, like a degree symbol
°
,ç
,ã
include
contains an array of object like:include: ["viewname1.view.lkml", "viewname2.view.lkml"]
- A dimension includes an
action" parameter
- A dimension/measure named 'yes' or 'no' or a reserved keyword
- A circular reference in the LookML
- A never ended
sql
parameter in the LookML - In a localization file (.strings), there is a wrong # to make a comment instead of a //
- In the aggregate table, the timezone is wrapped with [ ]
- A field that uses the
{% parameter parameter_name %}
Liquid variable is being listed in thefields
explore parameter. - You have a VPN enabled.
- You are using
create_process
inside of derived tables, without persisting them.
It's none of these!
You may be encountering some unexpected behavior.
If your Looker instance is self-hosted: Grab the Looker logs and search for a 500
event. If you find one, contact Looker Support to report the 500
event.
If your Looker instance is Looker-hosted: Submit a request through help.looker.com and a Looker Support analyst will reach out to you.
This content is subject to limited support.