Skip to main content
Last updated on

Troubleshoot Google Drive ingestion

This page describes common issues with the Google Drive connector in Databricks Lakeflow Connect and how to resolve them.

General pipeline troubleshooting​

If a pipeline fails while executing, click the step that failed and confirm whether the error message has sufficient information about the nature of the error.

View pipeline event logs in the UI

Check and download the cluster logs from the pipeline details page by clicking Update details in the right-hand pane, then clicking Logs. Scan the logs for errors or exceptions.

View pipeline update details in the UI

Authentication errors​

If you encounter OAuth errors, verify the following:

  • The OAuth client credentials (client ID and client secret) in the Unity Catalog connection are correct.
  • The OAuth consent screen is configured with the https://www.googleapis.com/auth/drive.readonly scope.
  • The Google account used to authenticate has access to the folder or drive configured in the pipeline URL.
  • The redirect URI in your Google Cloud OAuth client matches your Databricks instance URL. The redirect URI must be <databricks-instance-url>/login/oauth/google.html.

To re-authenticate, update the connection in Catalog Explorer with fresh OAuth credentials. See Set up Google Drive for managed ingestion.

Pipeline URL errors​

If the pipeline fails with an error indicating that the source URL is not accessible:

  • Confirm that the URL points to a folder or shared drive, not an individual file. The connector does not support individual file selection.
  • Verify that the Google account you used to create the connection has at least read access to the folder or drive at the configured URL.
  • Check that the folder or drive ID in the URL is correct by opening the URL in a browser with the same Google account.
On this page