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:- Navigate to Services Go to Settings > Services > Service Type (e.g., Database) in the OpenMetadata UI.
- Select a Service Choose the specific service for which you want to enable debug logging.
- 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.
- Enable Debug Logging In the configuration dialog, enable the Debug Log option and click Next.
- 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.Omni-Specific Issues
The following issues are specific to the Omni connector’s REST API integration.Authentication Failed (401)
Issue: The Test Connection step fails with a 401 error. Cause: Omni rejected the API token, it may be invalid, expired, or revoked, or Host and Port does not point at your Omni organization. Solution: Verify the token value and confirm it hasn’t been revoked in Omni. Confirm Host and Port points at your Omni organization, for examplehttps://your-org.omniapp.co. Regenerate the token in Omni and update the connection if authentication continues to fail.
Insufficient Permissions (403)
Issue: The Test Connection step fails with a 403 error. Cause: The token is valid but not authorized to read models and documents. Solution: Use an Organization API Key (or a Personal Access Token with sufficient access) that can read models and documents. See Requirements for how to generate one.Rate Limit Reached (429)
Issue: The Test Connection step or a metadata ingestion run fails or is delayed with a 429 error. Cause: Omni throttled the request. The default limit is 60 requests/minute. Solution: Wait and retry, or ask Omni to raise the rate limit for the API key. If this happens consistently during ingestion, narrow the Dashboard/Chart/Data Model/Project filter patterns to reduce the number of assets processed per run.TLS Verification Failed
Issue: The Test Connection step fails with an SSL/TLS certificate verification error. Cause: The server’s certificate could not be verified with the current SSL configuration. Solution: Provide the CA certificate under SSL Config with Verify SSL set tovalidate, or set Verify SSL to ignore for a self-signed certificate (not recommended outside of testing).
Connection Timeouts
Issue: The Test Connection step fails with a timeout or cannot reach the host. Cause: Host and Port is incorrect, includes a trailing/api (the connector appends this automatically), or the ingestion runner cannot reach your Omni instance over the network.
Solution: Verify Host and Port is correct and does not include a trailing /api. 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 SSL Config.