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

## Test connection returns 401

**Resolution**: Confirm that **API Key** contains a valid key for the dedicated service account. Replace the key if it is expired, revoked, or entered incorrectly.

## Test connection or aggregation returns 403

**Resolution**: Grant the permission named in the error, such as `SpaceView`, in the affected space. Refer to [Required Permissions](<https://documentation.sailpoint.com/connectors/octopus_deploy/saas/help/index.html#required-permissions>).

## Test connection returns a connectivity or TLS error

**Resolution**: Confirm that **Octopus Server URL** is an absolute HTTPS URL with a valid host and no extra path. Confirm that the certificate chain is trusted and the instance is reachable from SailPoint.

## Account aggregation returns no accounts

**Resolution**: Confirm that the service account can read Octopus Deploy users. Account aggregation includes only users whose `IsService` value is `false`.

## Entitlement aggregation returns no teams or user roles

**Resolution**: Confirm that the service account can read teams, user roles, scoped user roles, and team membership in each space.

## A dataset returns fewer objects than expected

**Resolution**: Confirm that the service account can read the resource type in each space. A transient or data error can cause the connector to skip one space and continue aggregating the others.

## Aggregation is slow or intermittently times out

**Resolution**: The connector retries HTTP 429 and server errors with backoff. If the problem continues, lower **Page Size** and confirm that the Octopus Deploy instance is healthy.

## Dataset information appears stale

**Resolution**: Datasets aggregate every 12 hours by default. Start an on-demand aggregation from the dataset's **Dataset Aggregation** page or adjust its schedule.