## Troubleshooting Looker connectivity

URL: https://docs.atlan.com/apps/connectors/business-intelligence/looker/troubleshooting/troubleshooting-looker-connectivity

> Learn about troubleshooting looker connectivity.

#### What are known limitations of Looker connector?

Following are the known limitations of the Looker connector:

- Persistent derived tables (PDTs) and Liquid parameterized tables are currently not supported for [Looker views](https://docs.atlan.com/llms/connectors/looker/what-does-atlan-crawl-from-looker/llms.txt).

#### What is timeframe for calculating `sourceViewCount` for Looks and dashboards?

The Atlan property `sourceViewCount` is based on the source property `view_count`:

- `view_count` displays a total count of views for a Look or dashboard since creation of the asset.
- Atlan currently doesn't support a timestamp for views due to limitations of the Looker APIs.

#### Why do I get 403 forbidden error after clicking test authentication button?

If you receive a 403 forbidden error when testing authentication, confirm the following:

- Verify you have provided the API host URL for Looker. (This may be different from the Looker instance URL.)
- Verify your Looker instance is running on port 433. If not, add the port number explicitly to the URL.
- Verify your client ID and secret are correct.
- Verify you have allowlisted the Atlan IP in your Looker instance. (To get details of your Atlan IP, please [raise a support ticket](https://docs.atlan.com/support/submit-request).)

Once you have confirmed or corrected these, retry the authentication.

#### Why is lineage missing from explore to tile or look?

If lineage is missing from an Explore to a Tile or Look, this is usually because you haven't [given content access to a folder](https://docs.atlan.com/llms/connectors/looker/set-up-looker/llms.txt).

Once you have corrected the access in Looker, rerun the Looker crawler in Atlan.

#### Why is lineage missing between data sources and Looker assets?

If lineage is missing from data sources to Looker assets, confirm the following:

- Verify you have given the `see_sql` permission to the role for which you [generated the API3 credentials](https://docs.atlan.com/llms/connectors/looker/set-up-looker/llms.txt).
- Verify you have crawled the data sources' assets in Atlan, _before_ crawling the Looker assets.

Once you have confirmed or corrected these, rerun the Looker crawler in Atlan.

#### Why is lineage missing from tables to models?

If lineage is missing from tables to models, this is usually because you have excluded a folder or project that contains these lineage details.

Once you have corrected this in the crawler configuration, rerun the Looker crawler in Atlan.

#### Why is relationship missing between models and queries, or Looks and models?

If a relationship is missing between some Looker assets, this is usually because you have excluded a project that contains these details.

Once you have corrected this in the crawler configuration, rerun the Looker crawler in Atlan.

#### Can I use deploy keys for setup?

[Deploy keys](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys#cons-of-deploy-keys) only grant access to a single repository. For more complex projects where Looker connects to multiple repositories, Atlan doesn't support using deploy keys.

#### Why am I seeing failed to clone project error?

```
Exception: ('Failed to clone project %s. Git URL: %s', '<project>', '<git_url>')
```

If you encounter this error, verify that the SSH key you’re using has access to all the GitHub project files included for crawling. Refer to the [Looker setup documentation](https://docs.atlan.com/llms/connectors/looker/set-up-looker/llms.txt) to learn more.

---