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

# Rill Troubleshooting Guide | OpenMetadata Support

> Troubleshoot Rill connector issues in OpenMetadata, including connection failures, authentication errors, and missing dashboards or lineage.

## 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 OpenMetadata. 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 OpenMetadata:

1. **Navigate to Services**
   Go to **Settings > Services > Service Type** (e.g., Database) in the OpenMetadata 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.

## Rill-Specific Issues

The following issues are specific to the Rill connector.

### Connection Fails Against a Rill Cloud Project

Rill Cloud requires authentication. If the test connection fails with an authorization error, confirm that an **API Token** is set and that it has read access to the project's resources. For a Rill Cloud project, **Host and Port** must point at the project endpoint (for example, `https://api.rilldata.com/v1/orgs/<org>/projects/<project>`).

### Branch-Level Routing Is Not Supported

The connector doesn't support Rill Cloud branch-level routing yet. If your project URL includes a `/branch/<name>` segment, remove it so **Host and Port** ends at the project (`.../projects/<project>`).

### No Dashboards, Charts, or Data Models Are Ingested

* Confirm the token has read access to the project's resources.
* Check your filter patterns. Overly broad exclusion rules, or include rules in **Only specific** mode, can filter out every dashboard, chart, or data model.

Rill exposes charts as the components used by **Canvas** dashboards. **Explore** dashboards don't define standalone components, so a project with only Explore dashboards produces no separate chart entities.

### Lineage to Source Tables Is Missing

Model-to-table lineage resolves a Rill model's SQL against tables already ingested in OpenMetadata. Make sure the upstream database service has been ingested first, and that the data model workflow is enabled so models and metrics views are extracted.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.