GITLAB_4

Issue

Glean was unable to fetch the members of one or more GitLab projects using the access token that was provided. Glean reads project members to enforce permissions, so the crawl cannot proceed until this check passes.

Resolution

• Confirm the personal access token is valid and not expired, and that it has the read scopes used during setup (read_user, read_api, read_repository).
• Confirm the token's user can access the projects in scope. The /members API only returns members for projects the token is allowed to see, so add the token's user to any project that is missing.

After updating the token on the GitLab data source setup page, save to re-validate.

If the problem persists, contact Glean Support.