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 GitLab from the Previews page. See Manage Azure Databricks previews.
This page describes common errors you might encounter with the managed GitLab connector and how to resolve them.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
A Premium or Ultimate feature table fails
Error message:
GitLab returned 403 for epics. Epics require a Premium or Ultimate group with the epics feature enabled.
GitLab returned 403 for iterations. Iterations require a Premium or Ultimate group with the feature enabled.
GitLab returned 403 for epic_boards. Epic boards require a Premium or Ultimate group with the epics feature enabled.
Cause: The epics, epic_issues, epic_boards, or group_iterations table was selected, but the group is not on a GitLab Premium or Ultimate tier, or the feature is not enabled.
Solution:
Remove the table from the pipeline, or upgrade the GitLab group to a tier that includes the feature. For the per-table tier requirements, see GitLab connector FAQ. GitLab returns the same message with a 404 code when the feature is not enabled.
An Ultimate security feature table fails
Error message:
GitLab returned 403 for vulnerabilities. Vulnerabilities require an Ultimate project with the security feature enabled.
GitLab returned 403 for compliance_frameworks. Compliance frameworks require an Ultimate group with the feature enabled.
Cause: The vulnerabilities or compliance_frameworks table was selected, but the project or group is not on the GitLab Ultimate tier, or the security feature is not enabled.
Solution:
Remove the table from the pipeline, or upgrade the GitLab project or group to Ultimate. The connector reports the same requirement when GitLab returns a GraphQL error for these tables.
The pipeline is rate limited
Cause: On gitlab.com, authenticated API traffic is limited to 2,000 requests per minute per user, and some endpoints have tighter per-endpoint limits. See GitLab rate limits. When GitLab returns 429, the connector waits for the interval in the Retry-After response header and retries.
Solution:
Reduce how frequently the pipeline runs, or ingest fewer tables per pipeline. See Ingest data from GitLab.