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.

​
Snowflake User Access Disabled

If you encounter the following error when attempting to connect to a Snowflake database:
This indicates that the Snowflake user account used for the connection has been disabled.

​
Resolution

  1. Log in to Snowflake using an account with administrative privileges.
  2. Run the following SQL command to re-enable the user:

​
No View Lineage Is Processed

The lineage agent log shows Processing View Lineage and then Lineage processing completed with 0/0 chunks processed, and no lineage is created for views, materialized views, or dynamic tables. 0/0 means the agent found no view definitions to process. Check the following:
  • Run the metadata agent first. The lineage agent reads view and dynamic table definitions from the Collate search index, so the metadata agent must have stored them and the search index must include them. If it doesn’t, run a search reindex. For more information, see Reindexing Search.
  • Confirm that the views or dynamic tables exist in Collate under the same service name as the lineage agent.
  • Check the database, schema, and table filter patterns of the lineage agent. Filtered-out views are skipped.
  • Confirm that Process View Lineage is on. If Incremental Lineage Processing is on, the agent skips views that it already processed in an earlier run, so a run with nothing new gives 0/0.
  • Confirm that the Snowflake role used by the metadata agent can read the definition. If the agent can’t fetch a definition, it ingests the table without one, and the lineage agent skips it.