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:

Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to Managing Additional Settings.

CircleCI returns 401

Resolution: Confirm that Personal API Token contains a valid CircleCI token. CircleCI API v2 does not support project tokens. A 401 response stops test connection and aggregation.

Test connection fails because the organization ID does not match

Resolution: Copy the UUID from CircleCI Organization Settings > Overview and enter it in Organization ID (UUID). The organization that CircleCI returns must match the value that you configure.

All project slugs are unreadable or invalid

Resolution: Confirm the slug format, such as gh/org/repo, bb/org/repo, or the CircleCI GitHub App or GitLab UUID form. Confirm that the token can read at least one configured project. Test connection requires a successful first-page pipeline probe. Empty context or pipeline lists are valid after the project probe succeeds.

Secret values are unavailable or masked

Resolution: Expect this behavior. The connector collects metadata only. It does not retrieve context environment variable secrets, and project environment variable and webhook signing secret values remain masked.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.