<br />

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 **Location** column 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](https://docs.cloud.google.com/looker/docs/2622/lookml-validation.md.txt)

Ex = [Explore](https://docs.cloud.google.com/looker/docs/2622/creating-and-editing-explores.md.txt)

SQL = [SQL Runner](https://docs.cloud.google.com/looker/docs/2622/sql-runner-basics)

LD = [LookML dashboard](https://docs.cloud.google.com/looker/docs/2622/reference/lookml-dashboard-overview)

D = [Dashboard](https://docs.cloud.google.com/looker/docs/2622/dashboards.md.txt)

S = [Schedules](https://docs.cloud.google.com/looker/docs/2622/scheduling)

A = [Admin](https://docs.cloud.google.com/looker/docs/2622/admin-panel-database-connections.md.txt)

| 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`. - When you're using Liquid variables or templated filters (such as `{% date_start %}`, `{% date_end %}`, or `{% condition %}`) inside a SQL-based persistent derived table's (PDT's) `derived_table` `sql` block, the referenced filter or parameter is not defined locally within the same view as the PDT. - In cascaded derived tables, an upstream derived table uses a view-level filter (such as a templated filter) referenced with Liquid, but the validation context for the downstream derived table does not include the Explore context of the upstream view. To resolve this, move the filter to a central, filter-only view (a view without a `sql_table_name` or `derived_table`), update the Liquid reference in the upstream table to use the fully scoped name (for example, `{% condition shared_filters.filter_name %}`), and use a bare join (`sql: ;;`) to join the filter-only view into the Explore. | - [Liquid variable reference](https://docs.cloud.google.com/looker/docs/2622/liquid-variable-reference.md.txt#getting_the_%E2%80%9Cvariable_not_found%E2%80%9D_error) - [Templated filters and derived tables (Community post)](https://www.googlecloudcommunity.com/gc/Technical-Tips-Tricks/Templated-Filters-and-Derived-Tables-Variable-not-found-quot/ta-p/587380) - [`from` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-from) - [`from` (for joins)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-join-from) - [Dimension groups must be referenced by their individual dimensions](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-dimension-group#dimension_groups_must_be_referenced_by_their_individual_dimensions) - [Cascading derived tables](https://docs.cloud.google.com/looker/docs/2622/derived-tables.md.txt#cascading_derived_tables) |
| `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. | - [Error: Unknown or inaccessible field (Best Practices page)](https://docs.cloud.google.com/looker/docs/best-practices/error-unknown-or-inaccessible-field) - [`from` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-from) - [`from` (for joins)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-join-from) |
| `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 (?).`](https://docs.cloud.google.com/looker/docs/2622/error-catalog.md.txt#Inaccessible_view_?_1) 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. | - [`fields` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-fields) - [`fields` (for joins)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-join-fields) - [Dimension groups must be referenced by their individual dimensions](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-dimension-group#dimension_groups_must_be_referenced_by_their_individual_dimensions) |
| `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. | - [`include` model parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-include) - [`extends` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-extends#definition) - [`explore` parameter](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-explore) - [Running a query against a LookML model in SQL Runner](https://docs.cloud.google.com/looker/docs/2622/sql-runner-create-queries-and-explores#running_a_query_against_a_lookml_model) |
| `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. | - [`extends` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-extends#definition) - [Scoping and naming LookML objects](https://docs.cloud.google.com/looker/docs/2622/sql-and-referring-to-lookml#scoping_and_naming) |
| `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. | - [Native derived table `explore_source` reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-explore-source#defining_a_native_derived_table) - [`filters` for LookML dashboards](https://docs.cloud.google.com/looker/docs/2622/reference/param-lookml-dashboard#filters-for-dashboard) - [`always_filter` reference](https://docs.cloud.google.com/looker/docs/2622/reference/explore-params/always_filter) - [`access_filter` reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-access-filter) - [`filters` for measures](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-filters) |
| `query failed: Invalid filter` | D | A dimension that was previously used as a filter in one or more dashboard tiles was deleted from the underlying LookML Explore. When you download the dashboard in PDF format, the filter attempts to evaluate but lacks the required reference dimension, causing the underlying query to fail. | To resolve the error and download the dashboard: <br /> 1. Edit the dashboard and check the individual tiles. Look for a yellow or red error message in the tiles that utilized the deleted filter. 2. Edit each affected tile. 3. Make a small change to the query (such as toggling a field or changing a sorting option) and re-save the tile to force Looker to clear the invalid filter reference. For more information about editing dashboards and tiles, see the [Editing user-defined dashboards](https://docs.cloud.google.com/looker/docs/2622/editing-user-defined-dashboards.md.txt) documentation page. |
| `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. | - [Measure type category reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-measure-types#measure_type_categories) - [Error: Measures with Looker aggregations (sum, average, min, max, list types) may not reference other measures (Best Practices page)](https://docs.cloud.google.com/looker/docs/best-practices/error-measures-with-looker-aggregations-reference-other-aggregations.md.txt) - [How to dimensionalize a measure in Looker (Best Practices page)](https://docs.cloud.google.com/looker/docs/best-practices/how-to-dimensionalize-a-measure.md.txt) |
| `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. | - [Trouble getting started with model/view/Explore (Community post)](https://www.googlecloudcommunity.com/gc/Modeling/Trouble-Getting-Started-with-Model-View-Explore/td-p/566554?postid=31043#post31043) - [`include` model parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-include) |
| `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 Tables** setting 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. | - [Testing database connections in Looker](https://docs.cloud.google.com/looker/docs/2622/admin-panel-database-connections.md.txt#testing_connections) - [Including files from an imported project](https://docs.cloud.google.com/looker/docs/2622/importing-projects.md.txt#including_files_from_an_imported_project) - [Persistent Derived Tables connection setting](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#persistent_derived_tables) - [OAuth for BigQuery connections](https://docs.cloud.google.com/looker/docs/2622/db-config-google-BigQuery#oauth_for_BigQuery_connections) - [OAuth for Snowflake connections](https://docs.cloud.google.com/looker/docs/2622/db-config-snowflake.md.txt#configuring_oauth_for_snowflake_connections) |
| `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. | - [Error: Unknown or inaccessible field (Best Practices page)](https://docs.cloud.google.com/looker/docs/best-practices/error-unknown-or-inaccessible-field) - [`suggest_dimension` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-suggest-dimension) - [`from` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-from) - [`from` (for joins)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-join-from) - [`fields` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-fields) - [`fields` (for joins)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-join-fields) |
| `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](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-view) |
| `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. | - [`include` model parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-include) - [Using `include` with IDE folders](https://docs.cloud.google.com/looker/docs/2622/ide-folders.md.txt#using_include_with_ide_folders) - [Including files from an imported project](https://docs.cloud.google.com/looker/docs/2622/importing-projects.md.txt#including_files_from_an_imported_project) - [Referencing files from an imported project](https://docs.cloud.google.com/looker/docs/2622/importing-projects.md.txt#referencing_files_from_an_imported_project) |
| `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. | - [Not all database dialects support `median` or `percentile` measure types with symmetric aggregates](https://docs.cloud.google.com/reference/explore-params/symmetric_aggregates#not_all_database_dialects_support_median_and_percentile_measure_types_with_symmetric_aggregates) - [Understanding Symmetric Aggregates (Best Practices page)](https://docs.cloud.google.com/looker/docs/best-practices/understanding-symmetric-aggregates.md.txt) |
| `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`](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-explore-source#using_bind_all_filters) |
| `Measures of type count don't 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 don't require a `sql` parameter. | - [`count` measure type reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-measure-types#count) - [How to count a non-primary key (Community post)](https://www.googlecloudcommunity.com/gc/Technical-Tips-Tricks/How-to-count-a-non-primary-key/ta-p/587307) |
| `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.* | - [`explore` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-explore) - [Including models in a model](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-include#including_models_in_a_model) |
| `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. | - [Using `include` with IDE folders](https://docs.cloud.google.com/looker/docs/2622/ide-folders.md.txt#using_include_with_ide_folders) - [`include` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-include) - [You can join the same table more than once using `from`](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-join#you_can_join_the_same_table_more_than_once_using_from) |
| `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. | - [Error: Unknown or inaccessible field (Best Practices page)](https://docs.cloud.google.com/looker/docs/best-practices/error-unknown-or-inaccessible-field) - [`from` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-from) - [`from` (for joins)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-join-from) - [`required_fields` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-required-fields) |
| `Cannot use (?) as access filter since any user can edit their own value.` | Ex | A user attribute with the **User Access** option set to **Edit** is used in an Explore's `access_filter` parameter. | - [Creating user attributes](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-user-attributes.md.txt#creating_user_attributes) - [Using user attributes in access filters](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-user-attributes.md.txt#access_filters) - [`access_filter` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-access-filter) |
| `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. | - [`label_from_parameter` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-label-from-parameter) - [`parameter` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-parameter) |
| `Cannot use user-editable attribute (?) for access_grant (?)` | IDE Ex | A user attribute with the **User Access** option set to **Edit** is used in a model file's `access_grant` parameter. | - [Creating user attributes](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-user-attributes.md.txt#creating_user_attributes) - [Controlling access with access grants](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-user-attributes.md.txt#controlling_access_with_access_grants) - [`access_grant` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-access-grant) |
| `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 overrides** column is not configured for a separate database user for PDT processes. | - [Using user attributes in database connections](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-user-attributes.md.txt#database_connections) - [Configuring separate login credentials for PDT processes](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#pdt-overrides) - [`datagroup` and `sql_trigger` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-datagroup#sql_trigger) |
| `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](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-join-relationship) |
| `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](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-distribution-style) |
| `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. | - [Error: Unknown or inaccessible field (Best Practices page)](https://docs.cloud.google.com/looker/docs/best-practices/error-unknown-or-inaccessible-field) - [Dimension groups must be referenced by their individual dimensions](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-dimension-group#dimension_groups_must_be_referenced_by_their_individual_dimensions) - [`always_filter` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-always-filter) |
| `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](https://docs.cloud.google.com/looker/docs/2622/reference/param-dimension-filter-parameter-types#location) |
| `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](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-create-process) |
| `Can't construct aggregate table (?), temporary schema for (?) is unset.` | IDE Ex | The **Persistent Derived Tables** setting is not set for the connection on the **Connection Settings** page in the **Admin** panel, and/or there is no temp database schema specified in the **Temp Database** setting. | - [Persistent Derived Tables connection setting reference](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#persistent_derived_tables) - [Temp Database connection setting reference](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#temp_database) |
| `Can't construct aggregate table (?), connection (?) could not be registered.` | IDE Ex | The **Temp Database** setting is not set on the connection's **Connection Settings** page in the **Admin** panel, or Looker does not have the appropriate permissions to the temp database specified in the **Temp Database** setting. | - [Aggregate tables must be persisted](https://docs.cloud.google.com/looker/docs/2622/aggregate_awareness.md.txt#aggregate_tables_must_be_persisted) - [Temp Database connection setting reference](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#temp_database) |
| `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 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. | - [`include` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-include) - [Using `include` with IDE folders](https://docs.cloud.google.com/looker/docs/2622/ide-folders.md.txt#using_include_with_ide_folders) - [`extends` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-extends#definition) - [`view_name` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-view-name) |
| `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](https://docs.cloud.google.com/looker/docs/2622/reference/param-dimension-filter-parameter-types#location) |
| `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](https://docs.cloud.google.com/looker/docs/2622/reference/param-measure-types#list) |
| `Query failed with unexpected exception (?)` | IDE Ex SQL LD D S | - A database other than the main connection database is specified in the **PDT Overrides** column on a connection's **Connection Settings** page in the **Admin** panel. - 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. | - [Configuring separate login credentials for PDT processes](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#pdt-overrides) - [Connection Pool Timeout](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#connection_pool_timeout) - [Looker startup options](https://docs.cloud.google.com/looker/docs/2622/startup-options) - [Query timeouts and queueing](https://docs.cloud.google.com/looker/docs/2622/admin-panel-database-queries.md.txt#query_timeouts_and_queueing) - [Connection settings additional params (including JDBC parameters)](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#additional_params) |
| `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. | - [What does the "Looker is having trouble connecting to your database" error mean? (Community post)](https://www.googlecloudcommunity.com/gc/Administering-Looker/What-does-the-quot-Looker-is-having-trouble-connecting-to-your/td-p/591967) - [Max Connections connection setting reference](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#max_connections) - [Connection Pool connection setting reference](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#connection_pool_timeout) |
| `FATAL: Too many connections for user '(?)'` | Ex SQL | The connection limit for the specified database user (for example, the dedicated `looker` user) has been reached on the database side. The database refuses new connections from Looker because Looker is attempting to establish more connections than are permitted for that specific user. | - Increase the connection limit for the dedicated user on the database side. - Verify that the [**Max connections per node**](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#max-connections) setting in Looker (**Admin** \> **Connections**) is configured to align with the connection limits that are imposed by the database to prevent connection exhaustion. |
| `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](https://docs.cloud.google.com/looker/docs/2622/incremental-pdts.md.txt#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](https://docs.cloud.google.com/looker/docs/2622/creating-visualizations.md.txt#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`. | - [`filters` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-filters) - [Creating a dynamic filtered measure](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-filters#creating_a_dynamic_filtered_measure) |
| `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. | - [`test` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-test) - [`explore_source` (for data tests)](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-test#explore_source) - [LookML data tests recommendations and best practices (Community post)](https://www.googlecloudcommunity.com/gc/Administering-Looker/What-does-the-quot-Looker-is-having-trouble-connecting-to-your/td-p/591967) |
| `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`. | - [`filter_expression` LookML dashboard query parameter reference (for waterfall chart)](https://docs.cloud.google.com/looker/docs/2622/reference/param-lookml-dashboard-waterfall-chart#filter_expression) - [LookML dashboard query parameter reference (for table chart)](https://docs.cloud.google.com/looker/docs/2622/reference/param-lookml-dashboard-table-chart#filter_expression) |
| `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 | - [Dimension and measure fields](https://docs.cloud.google.com/looker/docs/2622/lookml-terms-and-concepts.md.txt#dimension_and_measure_fields) - [`sql` (for dimensions)](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-sql) |
| `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`. | - [`view` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-view) - [`sql_table_name` (for views)](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-sql-table-name) - [`derived_table` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-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. | - [Things to consider when deciding whether to persist a derived table](https://docs.cloud.google.com/looker/docs/2622/derived-tables.md.txt#things_to_consider_when_deciding_whether_or_not_to_persist_a_derived_table) - [`access_filter` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-access-filter) |
| `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. | - [Dialect support for `distribution_style`](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-distribution-style#dialect_support_for_distribution_style) - [Dialect support for `cluster_keys`](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-cluster-keys#dialect_support_for_cluster_keys) - [`dimension_group` field type reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-dimension-group) - [`sql_distinct_key` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-sql-distinct-key) |
| `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](https://docs.cloud.google.com/looker/docs/2622/importing-projects.md.txt#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`. | - [`primary_key` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-primary-key) - [`extends` (for views)](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-extends) - [Reusing code with extends](https://docs.cloud.google.com/looker/docs/2622/reusing-code-with-extends) |
| `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. | - [Things to consider when deciding whether to persist a derived table](https://docs.cloud.google.com/looker/docs/2622/derived-tables.md.txt#things_to_consider_when_deciding_whether_or_not_to_persist_a_derived_table) - [`access_filter` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-access-filter) - [`sql_always_where` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-sql-always-where) - [Creating native derived tables](https://docs.cloud.google.com/looker/docs/2622/creating-ndts.md.txt) - [Aggregate awareness](https://docs.cloud.google.com/looker/docs/2622/aggregate_awareness.md.txt) |
| `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. | - [`map_layer` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-map-layer) - [Built-in map layers for `map_layer_name`](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-map-layer-name#built-in_map_layers) |
| `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. | - [`indexes` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-view-indexes) - [Persistent derived tables reference](https://docs.cloud.google.com/looker/docs/2622/derived-tables.md.txt#persistent-derived-tables) - [`aggregate_table` parameter reference](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-aggregate-table) |
| `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](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-sql). 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)](https://www.googlecloudcommunity.com/gc/Technical-Tips-Tricks/Common-SQL-error-troubleshooting-tips-in-Looker/ta-p/586852) |
| `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](https://docs.cloud.google.com/looker/docs/2622/google-maintenance-policy-for-looker-hosted-services.md.txt) |
| `Test database_version failed - No test result available` | A | When you're configuring a BigQuery database connection, an incorrect or a mistyped **Project ID** is specified in the **PDT Overrides** section on the **Connection Settings** page. The invalid Project ID causes the connection test to fail when it's evaluating the PDT environment. | Review your BigQuery connection settings, navigate to the **Persistent Derived Tables (PDT)** section, and verify that the Project ID entered is correct and that the configured service account has access to it. <br /> - [PDT overrides for BigQuery connections](https://docs.cloud.google.com/looker/docs/2622/db-config-google-BigQuery#pdt-overrides) - [Testing database connections in Looker](https://docs.cloud.google.com/looker/docs/2622/admin-panel-database-connections.md.txt#testing_connections) - [Configuring separate login credentials for PDT processes](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#pdt-overrides) |
| `SCHEMA_RESOLUTION: failed due to INTERNAL error` | Ex | When you're using Conversational Analytics on a very large Explore (for example, an Explore with more than 5,000 fields), the schema resolution process hits an internal payload limit and times out while attempting to map metadata for all available fields in the Explore. The UI might display no error message or display *I am unable to provide details about the data because I cannot access the necessary schema information*, while browser developer tools show `SCHEMA_RESOLUTION: failed due to INTERNAL error`. | To resolve the error, reduce the schema size and payload for Conversational Analytics by using one or more of the following methods: - **Create a dedicated Explore**: Build a refined or extended version of the Explore that is designed for Conversational Analytics that includes only necessary dimensions and measures. - **Use the `fields` parameter**: Restrict the fields that are available in the Explore by explicitly defining included fields or excluding unused fields in the LookML model. - **Hide unused fields** : Apply `hidden: yes` to dimensions and measures that are used only for backend joins, system keys, or calculations. For more information, see these references: <!-- --> - [LookML best practices for Conversational Analytics](https://docs.cloud.google.com/looker/docs/2622/conversational-analytics-looker-best-practices.md.txt#lookml-best-practices-for-conversational-analytics) - [`fields` (for Explores)](https://docs.cloud.google.com/looker/docs/2622/reference/param-explore-fields) - [`hidden` (for fields)](https://docs.cloud.google.com/looker/docs/2622/reference/param-field-hidden) |