Skip to main content

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.

Tableau Pipeline-Specific Issues

The following issues are specific to the Tableau Pipeline connector.

Test Connection Fails on a Specific Step

The test runs these steps: GetPipelines is required, and GetRuns, GetJobs, and GetLineage are optional.
  • GetPipelines: OpenMetadata can’t list the Tableau Prep flows available to the user. Confirm Host and Port, the credentials, and Site Name.
  • GetRuns: OpenMetadata can’t list flow runs. Non-administrators see only the runs of flows they can view.
  • GetJobs: OpenMetadata can’t list the extract refresh jobs of the site. Reading refresh job history requires a site administrator.
  • GetLineage: OpenMetadata can’t query flows through the Tableau Metadata API. Confirm the Metadata API is enabled on your Tableau server.

No Lineage Is Produced

Lineage needs the Tableau Metadata API. If it is not enabled, metadata and run status still ingest, but OpenMetadata draws no lineage edges. See Start the Metadata API. If the Metadata API is enabled and edges are still missing:
  • Tables not found: OpenMetadata matches tables against ingested database services. Ingest the source database service first, and set Database Service Names List under Lineage Information to limit the search to the right services.
  • Published data sources not found: OpenMetadata links published data sources to the data models created by the Tableau dashboard connector. Run the dashboard connector first.
  • Ambiguous input and output pairs: When a flow has several inputs and several outputs, Tableau must report which input feeds which output. If it does not, OpenMetadata draws no input to output edge for that flow and logs a warning that names it.

No Extract Refresh Status

Tableau answers extract refresh job queries only for server and site administrators. With another user, OpenMetadata still ingests extract refresh pipelines for the refresh tasks the user owns, but without run status. To skip extract refreshes entirely, turn off Include Extract Refreshes.

Scheduled Flows Do Not Appear to Run

Flows can run manually without Data Management, but scheduled runs need Tableau Prep Conductor. Without it, only manual runs appear as pipeline status.