# 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>).

## Account aggregation failing with "connector process may have crashed"

**Resolution** - Add `aggregateTimeout` in application to resolve the issue.

```json
[
    {
        "op": "replace",
        "path": "/connectorAttributes/aggregateTimeout",
        "value": 3600
    }
]
```

## 502 error during account aggregation

An account aggregation process fails with the following error message:

```text
java.lang.IllegalStateException: [ConnectorError] 502 Unknown error: {"data":null,"errors":[{"message":"Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug.
```

**Resolution** - If you continue to encounter the error, continue to reduce the page size setting until the process is successful. For example, reduce the page size incrementally from 100 to 50, then to 40, 30, and 20.

## GitHub Roles not aggregating correctly

GitHub roles associated with an account are not aggregating properly in SailPoint.

**Resolution** - Change the Role attribute type from `String` to `Role` in Account Schema . Save and re-aggregate the source.

## Account aggregation failing with error: Resource limits for this query exceeded with HTTP 429

During account aggregation, the process fails and returns an HTTP 429 error, indicating that the resource or API rate limits have been exceeded.

**Resolution** - If you continue to encounter the error, continue to reduce the page size setting until the process is successful. For example, reduce the page size incrementally from 100 to 50, then to 40, 30, and 20.

## Teams provisioning fails for a new user when no role is assigned

```text
[ConnectorError] Account updates failed. Cannot read properties of undefined (reading 'role')
```

**Resolution** -

- A user must be an active member of the GitHub organization with at least a base role (Member or Owner) before a team can be assigned.
- Instruct the user to accept the GitHub organization invitation.
- Once the user accepts and a role is assigned, team provisioning will complete successfully.
- Verify if the user currently has a role assigned in the GitHub organization.

## Provisioning may fail intermittently with the error ''sp-connect command timed out''

**Resolution** - Increase the timeout configuration values and retry the provisioning workflow:

- Set `aggregateTimeout` to 3600 seconds.
- Set `provisioningTimeout` to 600 seconds.

After updating these values, re-run the provisioning use case to confirm successful completion.

```json
[
  {
    "op": "add",
    "path": "/connectorAttributes/aggregateTimeout",
    "value": "3600"
  },
  {
    "op": "replace",
    "path": "/connectorAttributes/provisioningTimeout",
    "value": "600"
  }
]
```