# Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

- [SailPoint Identity Services Documentation](<https://documentation.sailpoint.com/saas/help/index.html>)
- [SailPoint Support Knowledge Base](<https://support.sailpoint.com/csm?id=kb_view2&amp;kb_id=05ff44289f011200550bf7b6077fcfa3>)
- [SailPoint Developer Community](<https://developer.sailpoint.com/>)

## Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](<https://documentation.sailpoint.com/saas/help/sources/managing_additional_settings.html>).

## The configured token is not a GitLab group access token

**Issue:** Authentication Type is set to Group Access Token, but the token supplied is a personal access token.

**Resolution:** Supply a group access token. Or change Authentication Type to Personal Access Token and configure target groups.

## The configured token is a group or project access token, not a personal access token

**Issue:** Authentication Type is set to Personal Access Token, but the token supplied is a group or project access token.

**Resolution:** Supply a personal access token. Project access tokens are not supported as a source credential.

## Target groups are required

**Issue:** The source uses a personal access token on gitlab.com, and Target Groups is empty.

**Resolution:** Enter the groups you want to aggregate. Refer to [Connection Settings](<https://documentation.sailpoint.com/connectors/gitlab/saas/help/connecting.html#connection-settings>).

## Target groups are not allowed with a group access token

**Issue:** Target Groups is set, but the source uses a group access token.

**Resolution:** Clear Target Groups. A group access token is confined to one group, which the source discovers.

## The token belongs to no group

**Issue:** A group access token, or a non-administrator personal token, belongs to no group. Nothing is in scope to aggregate.

**Resolution:** Grant the token membership of the groups you want to govern.

## Accounts appear as deleted after a previously successful run

**Issue:** Accounts that aggregated successfully now appear as deleted.

**Resolution:** The token might have lost instance administrator rights. This narrows the scope from the whole instance to the groups it belongs to. Check the connector log. It records the resolved scope at the start of every run. Restore the rights, or set target groups explicitly.

## Groups or projects are missing from a run

**Issue:** Some groups or projects do not appear in the aggregation results.

**Resolution:** The token most likely lacks the role that listing requires. GitLab refuses the listing. The source skips that node and logs it rather than failing the run. Check the log for skipped nodes. Compare them against the role table in [Prerequisites](<https://documentation.sailpoint.com/connectors/gitlab/saas/help/index.html#prerequisites>).

## Fewer machine identities than expected

**Issue:** The source returns fewer machine identities than expected.

**Resolution:** Service accounts and the credentials inventory need Premium or Ultimate. Group and project token listings need Owner or Maintainer. The source logs the resolved scope at the start of each aggregation. It logs the row and skip counts at the end. Check those two lines first.