​

Connection Issues

Connection failures are usually about scope, not syntax. Use this page to check the current product expectations before you assume the integration itself is broken.

​

Git Problems

​

GitHub

• Verify the app install completed
• Verify the right account or organization was chosen
• Verify the repositories you need were actually granted

​

GitLab

• Verify OAuth completed
• Verify the PENDING_USER_ACTION step 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 first
• Do not default to the deprecated manual path after October 1, 2025

​

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 actually grants read access where needed

​

A Good Rule

If the integration exists but produces nothing useful, the integration record is probably fine and the scope is probably wrong.

​

Next

Return to Connect a Git provider or Connect cloud accounts for the intended setup shape.