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

# Neo4j Troubleshooting | OpenMetadata Connector

> Troubleshoot common Neo4j connector issues in OpenMetadata, including connection failures, permission errors, and ingestion problems.

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

## Neo4j-Specific Issues

The following issues are specific to the Neo4j connector.

### Authentication Failed

Neo4j rejected the credentials. Confirm the **Username** and **Password**, and confirm that the user isn't suspended.

### Database Not Found

Neo4j can't find the database. Confirm the **Database Name**, or leave it blank to use the home database of the user.

### Insufficient Privileges

The user isn't allowed to read the graph schema. Grant the user `ACCESS` on the database and `EXECUTE` on the `db.schema.*` procedures, `db.labels`, and `db.relationshipTypes`. The built-in `reader` role covers these.

### Certificate Not Trusted

A connection that uses Transport Layer Security (TLS) fails with "certificate verify failed" when the server uses a self-signed certificate. Use a `neo4j+ssc` or `bolt+ssc` **Connection Scheme**, which accepts self-signed certificates. Alternatively, install the certificate authority that issued the certificate on the host that runs the ingestion.

### Neo4j Is Unavailable

The server didn't accept a Bolt connection. Confirm the **Connection Scheme**, confirm the **Host and Port**, and confirm that the server is running. Neo4j Aura requires the `neo4j+s` scheme.

### Invalid Connection Configuration

Neo4j rejected the connection configuration. Check the **Connection Scheme** and the **Host and Port**.

### Columns Show the UNKNOWN Data Type

A property that has more than one type, or a type that OpenMetadata doesn't recognize, is ingested as the `UNKNOWN` data type. Ingestion doesn't fail.

### A Schema Failed to Ingest

If OpenMetadata can't read the `nodes` or the `relationships` schema, it reports the failure in the ingestion status and keeps the assets that it already ingested for that schema.


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