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 Collate. 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 Collate:
  1. Navigate to Connections Go to Connections > Service Type (e.g., Database) in the Collate 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.

​
Prefect-Specific Issues

​
Authentication Failed on Prefect Cloud

Symptom: The Test Connection step fails with a 401 or 403 error. Cause: The API key is invalid, expired, or does not belong to the configured Account ID and Workspace ID, or lacks Viewer access to the workspace. Resolution: Verify the API key is valid and unexpired in your Prefect Cloud account settings. Confirm the Account ID and Workspace ID by checking the workspace URL: app.prefect.cloud/account/<accountId>/workspace/<workspaceId>.

​
Authentication Failed on Self-Hosted Server

Symptom: The Test Connection step fails with a 401 or 403 error against a self-hosted Prefect Server. Cause: The Basic Auth String does not match the server’s PREFECT_SERVER_API_AUTH_STRING, or the field was left empty while the server has auth enabled. Resolution: Confirm the user:password value configured as the Basic Auth String matches the PREFECT_SERVER_API_AUTH_STRING environment variable on the server. If the server has no auth enabled, leave the field empty.

​
No Flows Ingested

Symptom: The connector runs successfully but no Pipeline entities are created in Collate. Cause: The configured workspace (Cloud) or server (self-hosted) has no flows, or the Pipeline Filter Pattern excludes all of them. Resolution: Confirm flows exist in the target workspace or server. Review the Pipeline Filter Pattern includes and excludes rules and ensure at least one flow name matches an include rule (or that the filter is left empty to include all).

​
No Lineage Between Tables

Symptom: Flows and their run history are ingested, but no table-to-table lineage edges appear in Collate. Cause: On Prefect Cloud, the flow’s runs have no asset materializations (the flow doesn’t use @materialize or asset_deps). On both Cloud and self-hosted, the fallback lineage tags are missing, malformed, or the Database Service Name(s) is not configured in the pipeline service’s lineage settings. Resolution:
  1. For asset-based lineage (Prefect Cloud only), confirm the flow uses Prefect’s Assets API with @materialize or asset_deps.
  2. For tag-based lineage, confirm the tag format is exactly om-source:<database>.<schema>.<table> and om-destination:<database>.<schema>.<table> (three dot-separated parts). Verify the tagged tables exist in Collate under the database service(s) configured in the pipeline service’s lineage settings.