<br />

## Usage

```
new_lookml_runtime: yes
```

|---|---|
| Hierarchy [Manifest File](https://docs.cloud.google.com/looker/docs/2520/reference/param-project-manifest) `new_lookml_runtime` | Default Value Yes <br /> |

## Definition

> [!CAUTION]
> **Caution:** Using the legacy LookML runtime is highly discouraged, especially for [Looker (Google Cloud core)](https://docs.cloud.google.com/looker/docs/looker-core-overview) instances.

The new LookML runtime provides faster [LookML validation](https://docs.cloud.google.com/looker/docs/2520/lookml-validation#validating_your_lookml) and [content validation](https://docs.cloud.google.com/looker/docs/2520/content-validation), more performant loading of [Explores](https://docs.cloud.google.com/looker/docs/2520/creating-and-editing-explores) and [dashboards](https://docs.cloud.google.com/looker/docs/2520/viewing-dashboards), and faster SQL query writing, among other performance improvements.

You can use the `new_lookml_runtime` parameter to override your Looker instance's default LookML runtime. The default runtime for projects on your instance is configured with the [**Use Legacy LookML Runtime**](https://docs.cloud.google.com/looker/docs/2520/legacy-feature-schedule#new_lookml_runtime) legacy toggle:

- If the **Use Legacy LookML Runtime** legacy feature is enabled, projects on the instance will use the legacy LookML runtime by default. LookML developers can add `new_lookml_runtime: yes` to a project to override the instance default and enable the new LookML runtime for the project.
- If the **Use Legacy LookML Runtime** legacy feature is disabled, projects on the instance will use the new LookML runtime by default. LookML developers can add `new_lookml_runtime: no` to a project to override the instance default and use the legacy LookML runtime.

For example, if the **Use Legacy LookML Runtime** legacy feature is disabled for your instance, you can add the `new_lookml_runtime: no` statement to the project's [manifest file](https://docs.cloud.google.com/looker/docs/2520/reference/param-project-manifest) to use the legacy LookML runtime for the project:

    new_lookml_runtime: no

If your project does not have a manifest file, you can [create one](https://docs.cloud.google.com/looker/docs/2520/other-project-files#creating_a_manifest_file) using the Looker IDE.

## Considerations

When the new LookML runtime is enabled for a project, the LookML validator may catch previously overlooked errors. See the [Error: Unknown or Inaccessible Field](https://docs.cloud.google.com/looker/docs/2520/best-practices/error-unknown-or-inaccessible-field) Best Practices page for more information on how to resolve these errors.