## Troubleshooting Omni connectivity

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

> Learn about troubleshooting Omni connectivity, including authentication, permissions, and missing lineage.

## Why does test authentication fail?

If the connection test fails when you [provide your Omni credentials](https://docs.atlan.com/llms/connectors/omni/crawl-omni/llms.txt), check the following:

- The **Omni API base URL** must include the `/api` suffix and no trailing slash—for example `https://your-org.omniapp.co/api`, not `https://your-org.omniapp.co`.
- The **Omni API Token** must be a valid, unrevoked API key in the format `omni_osk_...`, generated under **Settings** > **API Keys** in Omni.
- The Omni user that owns the API key must still be active in your Omni organization.

## Why is my Omni catalog incomplete after crawl?

Omni API keys inherit the permissions of the Omni user that created them, so a key created by a user without organization-wide read access returns only the models, topics, folders, and documents that user can see. Regenerate the key from a user with organization-wide read access—see the recommended [service-user approach](https://docs.atlan.com/llms/connectors/omni/set-up-omni/llms.txt).

## Why don't I see warehouse → Omni lineage in graph?

Warehouse → Omni lineage is only emitted when the **Atlan source-connection map** is configured. If lineage is missing:

- Confirm you populated the [Atlan source-connection map](https://docs.atlan.com/llms/connectors/omni/crawl-omni/llms.txt) field, mapping each Omni connection ID to the qualified name of the corresponding Atlan warehouse connection.
- Confirm the upstream warehouse connection (Snowflake, BigQuery, Redshift, Databricks, or another supported source) already exists in Atlan and has been crawled at least once, so its `Table` assets are present when the Omni App runs.
- Confirm the qualified names in the map are correct—they must match the warehouse connection's qualified name exactly (for example `default/snowflake/1234567890`).

## What are known limitations of Omni connector?

Atlan currently doesn't support the following:

- Column-level lineage between warehouse tables and [Omni topics](https://docs.atlan.com/llms/connectors/omni/what-does-atlan-crawl-from-omni/llms.txt)—lineage is table-level only.
- Writing Atlan terms, classifications, or owners back to Omni—the connector is read-only ingest.

---