Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Azure DevOps from the Previews page. See Manage Azure Databricks previews.
This page describes common errors you might encounter with the managed Azure DevOps connector and how to resolve them.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Access denied
Error message:
Access denied due to insufficient permission.
Cause: The service principal doesn't have the access level, project membership, or permissions that the requested table needs.
Solution:
Confirm that the service principal has the Basic access level and membership in the projects to ingest. See Add the service principal to Azure DevOps.
Requested resource not found
Error message:
Requested resource was not found. The object may have been deleted, or it may no longer be available.
Cause: The Organization value in the connection doesn't match an Azure DevOps organization, or an object was deleted while the connector read it.
Solution:
Confirm that the Organization value in the connection is the organization name only, not the full URL. See Create an Azure DevOps connection. If the value is correct, run the pipeline again.
Rate limit exceeded
Error message:
Rate limit exceeded. Try running the pipeline again after some time.
Cause: The service principal exceeded the Azure DevOps global consumption limit of 200 throughput units (TSTUs) in a sliding five-minute window. See Rate and usage limits.
Solution:
Run the pipeline again after some time, or schedule it less frequently. The connector waits for the time in the Retry-After response header before it retries.