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

# MongoDB Troubleshooting Guide | OpenMetadata Support

> Troubleshoot MongoDB integration errors such as connection failures, schema fetch issues, or metadata mismatches.

## 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 Ingestion Tab**
   Go to the **Ingestion 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.

## Resolving MongoDB Ingestion Failures

When attempting to connect OpenMetadata to MongoDB, particularly cloud-hosted or replica set deployments, you might encounter timeout errors or connection failures. Follow the steps below to identify and resolve these issues.

## 1. Verify Connection Scheme

### Cloud MongoDB (MongoDB Atlas)

Use the connection scheme `mongodb+srv` in the **Advanced Config > Connection Scheme** field.
Do **not** include the port in the host field.

**Example:**

```yaml theme={null}
hostPort: ahamove.mongodb.net
connectionScheme: mongodb+srv
```

## 2. Enable SSL for Encrypted Connections

If your connection string includes `ssl=true`, you must explicitly set SSL in the Connection Options.

```yaml theme={null}
connectionOptions:
  ssl: true
```

This is mandatory when connecting to clusters that enforce SSL/TLS encryption.

## 3. Inspect Debug Logs

Enable and review debug logs for more detailed error messages:

* Navigate to the ingestion workflow in the OpenMetadata UI
* Enable **Debug Log** in the configuration settings
* Check logs using the Docker CLI:

```bash theme={null}
docker logs <openmetadata-ingestion-container>
```

4. Check Docker Networking

Ensure that the OpenMetadata container is on the same network as the ingestion container, especially when running locally via Docker Compose.