Console
    Contact Us Start free

    Looker error catalog

    The following table is a collection of some common error messages surfaced in Looker, explanations of their underlying causes and where they occur, and troubleshooting resources. The errors appear according to how frequently they are reported to Looker Support, in descending order, starting with the greatest number of support requests at the top.

    The Locationcolumn indicates where in Looker the error message is displayed, and includes the following options (some errors can appear in more than one location in the product):

    IDE = LookML validator/IDE

    Ex = Explore

    SQL = SQL Runner

    LD = LookML dashboard

    D = Dashboard

    S = Schedules

    Error message
    Location
    Possible Causes
    Troubleshooting Resources
    Variable not found (?).
    IDE
    • The Liquid for variable reference, {{ }} , is nested within Liquid for logic, {% %} .
    • A templated filter references a table that is not joined into a derived table.
    • A field referenced in Liquid is not fully scoped with a view name ( view_name.field_name ).
    • A filter's value is referenced inside another LookML dashboard filter.
    • A parameter parameter's value is not compatible with the corresponding type . For example: { % if parameters.change_value._parameter_value == "'AA'" %} Review the parameter type to ensure that the value evaluates correctly ( type: string versus type: unquoted ).
    • A field is referenced correctly in Liquid as view_name.field_name , but field_name is not defined in the scoped view view_name , or the view is aliased with from in an Explore.
    • A Liquid reference to a variable is not defined, or the reference includes a typo.
    • A Liquid reference includes a dimension group of type: time , but not the specific timeframe. For example, instead of {{ view_name.creation_date }} , the reference should use {{ view_name.creation_date_year }} .
    • A field is using Liquid with LookML substitution operator syntax, ${view_name.field_name} , instead of without, as view_name.field_name .
    Inaccessible view (?). (?) is not accessible in explore (?). Check for missing joins in explore (?).
    IDE
    • The referenced view doesn't exist.
    • A join is missing, making the view inaccessible to some Explores.
    • The view is renamed with a from parameter in an Explore.
    Unknown or inaccessible field (?). Check for typos or append a timeframe to the name if the field is type time.
    IDE
    Any of the possible causes listed for the error Inaccessible view (?). (?) is not accessible in explore (?). Check for missing joins in explore (?). may apply, plus the following:
    • There is a typo in a field name or in a reference to the field.
    • The field is excluded from an Explore by the fields parameter.
    • The reference is to a dimension_group without a timeframe specified.
    Unknown view (?).
    IDE Ex SQL
    • A view is not included in the model file.
    • An explore is extending a base explore that is missing a view_name parameter.
    • An Explore name defined in the explore parameter is based on a misspelled or nonexistent view name.
    • A model-based SQL Runner query is running with the incorrect model selected.
    Unknown view (?). View does not exist in model (?). Check for typos or missing include statements.
    IDE Ex SQL
    • An explore is extending a base explore that is missing a view_name parameter, and fields from any of the joined views reference the base explore name.
    • A field references a view that is misspelled, nonexistent, or not joined to applicable Explores.
    Unknown field (?) in filter
    IDE
    • A native derived table (NDT) definition includes a bind_all_filters parameter on a custom field that is not defined in LookML.
    • A LookML filter references a LookML field that is commented out or that does not exist.
    • A LookML filter references a LookML field from a different view, and the field is not fully scoped nor joined into all relevant explore parameters.
    Measures with Looker aggregations (sum, average, min, max, list types) may not reference other measures.
    IDE
    A measure is referenced inside the SQL definition of another aggregate-type measure.
    Unknown view (?). View (?) does not exist in model (?). Check for typos or missing include statements in (?).
    IDE
    A view is not included in a model file, or it is included but is misspelled.
    Can't construct persistent derived table (?), connection (?) could not be registered
    IDE Ex
    • Any dependencies for an existing PDT have failed to build.
    • There is an issue with the connection, which needs to be diagnosed by testing the connection (for example, testing the connection may reveal that the Looker user may not have sufficient own or write access to the database).
    • Imported project files, such as a view that defines the failing PDT, or a view that is referenced by the failing PDT, are not included in the importing project.
    • The database connection does not have the Persistent Derived Tablessetting enabled.
    • A Looker Block's code has not been updated to the connection's SQL dialect, if different from the dialect for which the block was written.
    • OAuth is enabled for a Snowflake or BigQuery connection.
    • A value other than the default value, TRUE , has been set for the Snowflake database AUTOCOMMIT parameter.
    Unknown or excluded suggest_dimension (?) in field (?)
    IDE
    • A field referenced by a suggest_dimension parameter does not exist, has been commented out, or is excluded in an Explore by a fields parameter.
    • A field referenced by a suggest_dimension parameter is defined in another view, but is not fully scoped as view_name.field_name in the reference.
    • A suggest_dimension parameter references a field in a different view that is not joined into all relevant explore parameters, or a view that is aliased in an explore with a from parameter.
    A view named (?) has been defined multiple times. Each view in a model must have a unique name.
    IDE
    Views with identical names are referenced in the same model, including views imported into the project. View names must be unique in a model.
    view parameter reference
    This include does not match any files
    IDE
    • A typo in the path to the file is causing en error.
    • A folder reference is using incorrect syntax.
    • A project import reference is using incorrect syntax.
    SQL Dialect does not support Symmetric Aggregates with percentiles, field ignored.
    Ex
    The database dialect does not support measures of type: median or type: percentile with symmetric aggregates.
    Cannot use native derived table (?) with bind_all_filters outside of its source explore (?)
    IDE Ex
    A native derived table (NDT) with a bind_all_filters parameter is joined to one or more Explores other than the Explore defined in the explore_source parameter.
    Using bind_all_filters
    Measures of type count do not use the sql parameter. Use count_distinct to count by something other than the primary key, or remove the sql parameter.
    IDE
    A sql parameter is used in a measure of type: count . Count type measures perform a count by the primary key declared in the view file and do not require a sql parameter.
    An explore named (?) has been defined multiple times. Each explore in a model must have a unique name.
    IDE LD
    • An Explore name defined in the explore parameter of a model file is duplicating another existing Explore name. Explore names must be unique in a model.
    • An imported project has an explore with the same name as an existing explore in the importing project.
    • An included model file has an explore with the same name as an existing explore in the including project model file. *
    • There is a circular reference in the code, referencing the explore (or model file) multiple times.
    * It is not best practice to include model files in other model files.
    Unknown view '(?)' --> Did you '- include: (?)' in (?).model.lookml?
    IDE
    • A model is including the view folder, but the specific view file is outside the folder.
    • A model is including the name of the view, but not the view file, if named differently.
    • A view is joined into an explore multiple times, but is missing the from parameter the second time it is joined.
    Unknown field '(?)'
    IDE Ex
    • The field you are trying to reference does not exist, has been misspelled, or has been commented out.
    • A referenced field is defined in a different view, and is not scoped with its view name.
    • A field is defined in a different view that is not joined into the necessary Explores, or the view is aliased in a join, making the field inaccessible by some Explores.
    • A required_fields parameter references a field that is inaccessible, is misspelled, doesn't exist, or is commented out.
    Cannot use (?) as access filter since any user can edit their own value.
    Ex
    A user attribute with the User Accessoption set to Editis used in an Explore's access_filter parameter.
    label_from_parameter of (?) must refer to a parameter.
    IDE Ex
    • A field referenced by a label_from_parameter parameter doesn't exist, is misspelled, or is commented out.
    • A field referenced by a label_from_parameter parameter exists, but is not a parameter type.
    Cannot use user-editable attribute (?) for access_grant (?)
    IDE Ex
    A user attribute with the User Accessoption set to Editis used in a model file's access_grant parameter.
    datagroup (?) has a sql_trigger. This is not allowed in models with a parameterized connection.
    IDE
    A database connection is using user attributes for database login credentials, and the PDT overridescolumn is not configured for a separate database user for PDT processes.
    relationship missing, assumed to be many_to_one.
    IDE
    A join's relationship is not defined. When a relationship is not specified, Looker assumes a many-to-one relationship by default.
    relationship parameter reference
    No distribution_style specified in persistent derived table (?). Using default distribution style (?).
    IDE
    A Redshift connection PDT doesn't have a distribution_style parameter specified in its derived_table definition. When there isn't a distribution_style specified, Looker defaults to ALL .
    distribution_style parameter reference
    always_filter: unknown filter field '(?)'
    IDE
    • A field referenced by an always_filter parameter does not exist, is misspelled, or is commented out.
    • A field referenced by an always_filter parameter is a dimension_group of type: time that does not have a timeframe appended.
    • A field referenced by an always_filter parameter is a field that is defined in a view that is not joined into all relevant explore parameters, or the field is not scoped with its view name.
    The location field type requires both sql_latitude and sql_longitude.
    IDE
    A field of type: location is missing either the sql_latitude or the sql_longitude subparameter. Location type fields require both.
    location field type reference
    Missing required sql_step in create_process of derived table '(?)'.
    IDE
    • There is no sql_step specified in the create_process , which requires one or more sql_step subparameters.
    • A cached LookML validator error flagged a missing sql_step even though a sql_step was already added. Validate once more to resolve the error.
    create_process parameter reference
    Can't construct aggregate table (?), temporary schema for (?) is unset.
    IDE Ex
    The Persistent Derived Tablessetting is not set for the connection on the Connection Settingspage in the Adminpanel, and/or there is no temp database schema specified in the Temp Databasesetting.
    Can't construct aggregate table (?), connection (?) could not be registered.
    IDE Ex
    The Temp Databasesetting is not set on the connection's Connection Settingspage in the Adminpanel, or Looker does not have the appropriate permissions to the temp database specified in the Temp Databasesetting.
    Unknown view (?) referenced by explore (?)
    IDE
    • A view is included using the default include: "*.view.lkml" , but the view is in a different folder.
    • A view name or file path is misspelled in an include statement, or the include statement is including the name of the view, but not the view file, if named differently.
    • There is an issue with special characters, such as _views , in a folder.
    • An explore is extending another explore that is missing a view_name parameter that specifies the base view.
    The location field type does not use the sql parameter. Please use sql_latitude and sql_longitude instead.
    IDE
    A sql parameter is used in a field of type: location . Location type fields require sql_latitude and sql_longitude subparameters instead of the sql parameter.
    location field type reference
    A list_field must be defined for measures of type list.
    IDE Ex
    To generate a list from a field, the field must be specified for a measure of type: list .
    list field type reference
    Query failed with unexpected exception (?)
    IDE Ex SQL LD D S
    • A database other than the main connection database is specified in the PDT Overridescolumn on a connection's Connection Settingspage in the Adminpanel.
    • The per-user query limit has been exceeded and a queued query has hit the connection pool timeout.
    • A JDBC connection has failed.
    • An unexpected Looker application failure has occurred.
    Looker is having trouble connecting to your database.
    Ex SQL
    A connection's max connection pool limit has been reached, and queued queries have timed out after the connection pool timeout window has elapsed.
    SQL Error in incremental PDT: Query execution failed
    Ex D S
    The underlying schema has changed for one or more tables that were referenced in an SQL-based incremental PDT.
    Incremental PDT fails to build after schema change
    Missing dates/values for '(?)' were not filled.
    Ex
    • Dimension fill cannot be applied because more than one dimension was selected in an Explore.
    • Dimension fill cannot be applied because one or more fields were pivoted in an Explore.
    • Dimension fill cannot be applied because a field has distinct string values (for example, allowed_value or case parameters), and there is a filter applied to that field.
    Filling in missing dates and values
    filters: ` is not supported for measures of non-aggregate type '(?)'
    IDE Ex
    A filters parameter was used with any measure type other than the following: count , sum , average , and count_distinct .
    Unknown source explore (?) in lookml test (?) declaration.
    IDE
    • A misspelled, nonexistent, or commented-out Explore name is used in a data test's explore_source subparameter.
    • A data test is defined in a file that does not include or is not included in the file that contains the Explore's explore_source definition.
    • An Explore with the extension: required parameter specification is used as the explore_source of a data test.
    filter_expression: is not supported for measures of non-aggregate type '(?)'
    IDE Ex
    A filters_expression parameter was used with any measure type other than the following: count , sum , average , or count_distinct .
    Field references an aggregate but is specified as a dimension. If you want to use aggregations such as sum, average, count, use a measure type instead.
    IDE Ex
    A dimension references a measure or another aggregation in its sql parameter
    Cannot specify both sql_table_name and derived_table for view (?)
    IDE
    A view has both sql_table_name and derived_table parameters defined. A view can only reference one table — either an existing schema in the database connection with sql_table_name , or a new table with derived_table .
    Persistent Native Derived Table for view (?) has an explore source (?) that has access filters. Persisting this table may result in unexpected behavior.
    IDE
    A persisted NDT is based on an Explore with an access_filter parameter that references user attributes.
    Unknown or unexpected parameter "(?)" in (?).
    IDE
    • A distribution_style parameter is used for a dialect that does not support that parameter
    • A cluster_keys parameter is used for a dialect that does not support that parameter
    • A sql_always_where parameter is defined in a join instead of an explore .
    • Timeframes defined in a dimension_group are not of type: time .
    • A sql_distinct_key parameter is defined in a dimension instead of a measure.
    Could not find the constant
    IDE
    A constant is referenced from an imported project in an importing project, and is only defined in the imported project. Constants can only be referenced in the projects in which they are defined. The constant needs to be redefined in the manifest file.
    Using constants in files from an imported project
    Multiple primary key definitions for view '(?)': '(?)' and '(?)'
    IDE
    More than one primary key exists in a view file. Either more than one dimension is specified as a primary key with primary_key: yes , or an extending view specifies a new dimension as a primary key with primary_key: yes .
    Persistent Native Derived Table for view (?) references user attributes. Persisting this table may result in unexpected behavior.
    IDE
    A persisted NDT or an aggregate awareness table is based on an explore with an access_filter or sql_always_where parameter referencing user attributes.
    No map layer named (?) is defined. Must be one of countries, uk_postcode_areas, us_counties_fips, us_states, us_zipcode_tabulation_areas
    IDE
    A dimension references a map layer with map_layer_name when there is no map layer defined in all models in which the field's view is included. For example, a view is included in multiple models, but the map layer is defined in only one model.
    Persistent derived table (?) should include at least one index
    IDE
    A PDT or an aggregate table definition includes an index in which a PDT or an aggregate table column has not been specified.
    The x database encountered an error while running this query.
    Ex SQL
    The database cannot locate a column that is referenced by a field's sql parameter . This can be caused by one of the following conditions:
    • There is a typo in the table or column name that is referenced in a sql parameter.
    • The underlying data in the database, for example, a column name, has changed.
    Common SQL error troubleshooting tips in Looker (Community post)
    Render job (?) failed [orphaned job]
    S
    The Looker instance was unavailable during the time that the scheduled job ran. This can happen during version updates and scheduled maintenance.
    Google maintenance policy for Looker-hosted services
    Create a Mobile Website
    View Site in Mobile | Classic
    Share by: