> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Omni Troubleshooting

> Troubleshoot Omni connector issues related to authentication, lineage, or ingestion errors.

### Common Issues

#### Authentication Failures

* Verify that your API token is valid and hasn't expired.
* Confirm the token type matches the access you need: an Organization API key for org-wide access, or a Personal Access Token for your own access.
* Regenerate the token in Omni and update the connection if authentication continues to fail.

#### Connection Timeouts

* Verify the **Host and Port** is correct and doesn't include a trailing `/api`. Collate appends it automatically.
* Check network connectivity between the ingestion runner and your Omni instance.
* If your Omni instance sits behind an internal certificate authority, set **Verify SSL** to `validate` and provide the CA certificate under **Advanced Config**.

#### Missing Dashboards, Charts, or Data Models

* Check the **Dashboard Filter Pattern**, **Chart Filter Pattern**, **Data Model Filter Pattern**, and **Project Filter Pattern** for rules that might be excluding the assets you expect to see.
* Confirm the token has access to the project or folder the document lives in.

#### Missing Lineage

* Lineage depends on each Omni topic's declared base table matching a table Collate has already ingested. Ingest the source database service before running the Omni service, and confirm its schema and table names match what Omni's topic points to.
* Set **Db Service Prefixes** in the metadata agent's **Lineage Information** section to scope table matching to the correct database service.

## Troubleshooting

### Workflow Deployment Error

If there were any errors during the workflow deployment process, the
Ingestion Pipeline Entity will still be created, but no workflow will be
present in the Ingestion container.

* You can then Edit the Ingestion Pipeline and **Deploy** it again.
* From the Connection tab, you can also Edit the Service if needed.

## Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in Collate. Below are some of the most frequently observed troubleshooting scenarios.

## How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in Collate:

1. **Navigate to Connections**
   Go to **Connections** > **Service Type** (e.g., Database) in the Collate UI.

2. **Select a Service**
   Choose the specific service for which you want to enable debug logging.

3. **Access Agents Tab**
   Go to the **Agents tab** and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.

4. **Enable Debug Logging**
   In the configuration dialog, enable the **Debug Log** option and click **Next**.

5. **Schedule and Submit**
   Configure the schedule if needed and click **Submit** to apply the changes.

## Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.