Skip to main content

​
Common Issues

Most public-docs problems in Cloudgeni come from one of four places:
  • The provider connected, but the useful scope was never granted
  • The integration is active, but the repository or cloud account was never selected in the workflow
  • A scan finished, but you are looking in the wrong product surface
  • A review or agent workflow was assumed to be global when it is actually repository-level

​
Git Connected But No Repositories Show Up

Check:
  • The provider install or authorization scope
  • Any follow-up selection step for GitLab or Azure DevOps
  • The integration detail page, not just the list view

​
Cloud Connected But No Useful Data Appears

Check:
  • The account really has read access to the resources you expect
  • A sync or scan has been triggered after the integration became active
  • You are looking in the right surface: inventory, cloud monitors, or cloud compliance

​
PR Reviews Never Start

Check:
  • The repository-level PR review setting
  • The repository is under an active Git integration
  • Provider-side event delivery is healthy
Connecting the Git provider alone does not enable PR reviews.

​
Agent Session Lacks Context

Check the launch form. Connecting integrations earlier is not the same as attaching them to the session. If the agent seems blind to cloud or documentation context, verify those selectors were actually included when the run started.

​
Drift Feels Broken On Day One

That is usually a sequencing problem, not a drift bug. Do not start with configuration drift unless:
  • The repository is already meaningful
  • The cloud integration is already healthy
  • You trust the mapping between the two

​
Next

If the problem is specifically auth or provider setup, continue with Connection Issues.