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
- SailPoint Support Knowledge Base
- SailPoint Developer Community
Debug Logs
For information about managing additional source settings, including debug logging and downloading connector logs, refer to Managing Additional Settings.
Test connection returns 401
Resolution: Confirm that API Access Token contains a valid token with REST API access enabled. Replace the token if it is expired, revoked, or entered incorrectly.
Test connection returns 404 for the organization
Resolution: Confirm that Organization Slug matches the slug in your Buildkite URL, such as acme-inc in https://buildkite.com/acme-inc. Enter the slug, not the display name of the organization. Confirm that the token owner belongs to that organization.
Test connection reports missing scopes
Resolution: Edit or replace the token and grant each scope named in the error. Refer to Required Permissions.
Test connection cannot list organization members
Resolution: Confirm that the token owner belongs to the organization and can view its teams. Some Buildkite plans restrict team permissions.
Account aggregation returns no members
Resolution: Run test connection and confirm that the configured token has read_organizations and permission to list organization members. Confirm that the organization contains members.
Entitlement aggregation returns no teams
Resolution: Confirm that the token has read_teams. If Buildkite reports a plan limitation, update the organization plan to enable team permissions.
Agent token or secret aggregation returns no records
Resolution: Confirm that the organization contains clusters and that the token has read_clusters. Secret aggregation also requires read_secrets_details.
Registry token aggregation returns no records
Resolution: Confirm that the token has read_registries and that package registries are enabled for the Buildkite organization.
Aggregation returns 429 or runs slowly
Resolution: Buildkite applies shared rate limits per user and organization. Avoid overlapping manual and scheduled aggregations. Leave Page Size at 100 unless aggregation times out.
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.