Skip to main content
Last updated on

Troubleshoot Google Drive ingestion

Diagnose and fix common issues with the Google Drive connector in Databricks Lakeflow Connect, such as authentication errors and inaccessible pipeline URLs.

For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.

Authentication errors​

OAuth U2M: Databricks-managed​

Please verify that:

  • The Google account used to authenticate has access to the folder or drive configured in the pipeline URL.
  • The account completed the Google consent screen.

To re-authenticate, update the connection in Catalog Explorer. See Configure OAuth U2M: Databricks-managed for Google Drive ingestion.

OAuth U2M: Custom-managed​

Please verify that:

  • 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.
  • If the app has an External audience, the Google account used to authenticate is listed as a test user on your Google Cloud project.
  • 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 Configure OAuth U2M: Custom-managed for Google Drive ingestion.

OAuth service account​

Please verify that:

  • The service account key JSON in the Unity Catalog connection is complete and hasn't been revoked in the Google Cloud console.
  • The Google Drive API is enabled on the Google Cloud project that owns the service account.
  • The files, folders, or shared drives you want to ingest are shared with the service account's email address, with at least Viewer access.

To rotate credentials, create a new service account key and update the connection in Catalog Explorer. See Configure an OAuth service account for Google Drive 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 identity you used to create the connection has at least read access to the folder or drive at the configured URL.
  • For a service account connection, confirm that the content is shared with the service account's email address.
  • Check that the folder or drive ID in the URL is correct by opening the URL in a browser with an account that has access.
On this page