Connection Issues
Connection failures are usually about scope, not syntax. Check the connection scope and setup steps before reconnecting the integration.Git Problems
GitHub
- Verify the app install completed
- Verify the right account or organization was chosen
- Verify the repositories you need were granted
GitLab
- Verify OAuth completed
- Verify the
PENDING_USER_ACTIONstep was completed if it appeared - Verify you are thinking at the project level, not a vague group-wide level
Azure DevOps
- Verify the redirect completed
- Verify any follow-up confirmation or selection step completed
- Verify repositories appear on the integration detail page
Cloud Problems
AWS
- Verify the IAM user really has the read-only scope you intended
- Verify the access key pair is valid
Azure
- Use Quick Connect for an automated Azure consent flow, or Manual for an existing service principal
- If resources appear but Cost & Billing is empty, verify the service principal has
Cost Management Readeron the subscription and that Azure billing visibility is enabled for the subscription scope
GCP
- Prefer the impersonation path
- If using impersonation, verify the token creator binding for the Cloudgeni platform service account
- If using a service account key, verify the key matches the intended project
OCI
- Verify the OCIDs, fingerprint, and private key match the same dedicated user
- Verify the user’s group policy grants read access where needed