Skip to main content

​
Common Issues

This guide covers common issues you may encounter when using Cloudgeni and how to resolve them.

​
Repository Scanning Issues

Possible causes:
  • Repository not synced from git provider
  • Insufficient permissions on the repository
  • Repository is archived or disabled
Solutions:
  1. Go to Settings → IaC Repositories
  2. Click Refresh to sync repositories
  3. Verify you have at least read access to the repository
  4. Check if the repository is active (not archived)
Possible causes:
  • Files are in unsupported formats
  • Files are in excluded directories
  • Branch configuration is incorrect
Solutions:
  1. Verify files have supported extensions (.tf, .bicep, .hcl, .yaml, .json)
  2. Check scan path configuration in repository settings
  3. Ensure files are committed to the configured branch
  4. Review exclude patterns for accidental exclusions
Possible causes:
  • Large repository with many files
  • Network connectivity issues
  • Resource-intensive configurations
Solutions:
  1. Configure scan to target specific directories
  2. Exclude test/example directories
  3. Check network connectivity
  4. Contact support if scans consistently timeout
Common errors and solutions:
ErrorSolution
Authentication failedReconnect git provider
Repository not foundVerify repository exists and you have access
Branch not foundCheck branch name in settings
TimeoutReduce scan scope or contact support

​
Cloud Integration Issues

Possible causes:
  • Invalid credentials
  • Missing IAM permissions
  • Network/firewall restrictions
Solutions:
  1. Verify credentials are correct and not expired
  2. Check IAM role/policy has required permissions
  3. For AWS: Verify trust relationship includes Cloudgeni
  4. For Azure: Check app registration permissions
  5. See Connection Issues for provider-specific help
Possible causes:
  • Scan not completed
  • Region not included in scan
  • Resource type not supported
Solutions:
  1. Run a new cloud scan
  2. Check region configuration includes your resources
  3. Verify resource type is in supported list
  4. Check cloud account permissions for resource access
Possible causes:
  • Stale scan data
  • Permissions insufficient to read configurations
  • Resource excluded from scan
Solutions:
  1. Run a fresh compliance scan
  2. Verify cloud account has read permissions for all services
  3. Check resource isn’t excluded by filters
  4. Review finding details for specific issues

​
Pull Request Review Issues

Possible causes:
  • Webhook not configured
  • PR reviews disabled for repository
  • No IaC changes in the PR
Solutions:
  1. Verify webhooks are configured in git provider
  2. Check repository settings in Cloudgeni have PR reviews enabled
  3. Ensure PR contains changes to supported file types
  4. Check webhook delivery history in git provider
Possible causes:
  • Insufficient write permissions
  • Git provider API rate limiting
  • Review bot user blocked
Solutions:
  1. Verify Cloudgeni has write access to repository
  2. Wait for rate limit to reset
  3. Check if bot user is blocked in repository settings
  4. Reconnect git provider to refresh permissions
Solutions:
  1. Mark finding as false positive in Cloudgeni
  2. Add inline ignore comment in code: 
    # cloudgeni:ignore:CKV_AWS_19
resource "aws_s3_bucket" "example" { ... }
  3. Configure policy exceptions in organization settings
  4. Report false positive to Cloudgeni support

​
Remediation Issues

Possible causes:
  • Finding type not supported for auto-remediation
  • Complex configuration requires manual fix
  • Repository not connected
Solutions:
  1. Check if finding type supports auto-remediation
  2. Use AI DevOps agent for complex fixes
  3. Verify repository is connected and writable
  4. Review finding details for manual remediation steps
Possible causes:
  • Branch protection rules blocking
  • No write access to repository
  • Branch already exists
Solutions:
  1. Check branch protection allows Cloudgeni to create branches
  2. Verify write permissions on repository
  3. Delete conflicting branch or use different name
  4. Check git provider connection status
Possible causes:
  • Generated code has syntax errors
  • Missing dependencies
  • Configuration conflicts
Solutions:
  1. Review generated code before applying
  2. Check for missing variable definitions
  3. Verify provider configuration is complete
  4. Test locally with terraform validate or bicep build

​
API Issues

Common causes:
  • Invalid or expired API key
  • Wrong header name
  • Key doesn’t have required scope
Solutions:
  1. Verify API key is correct
  2. Use header name X-CLOUDGENI-API-KEY (not Authorization)
  3. Check key has required permissions
  4. Generate new key if expired
See API Authentication for details.
Solutions:
  1. Implement exponential backoff
  2. Cache responses where possible
  3. Use webhooks instead of polling
  4. Upgrade plan for higher limits
// Example retry logic
if (response.status === 429) {
  const retryAfter = response.headers.get('Retry-After');
  await sleep(retryAfter * 1000);
  return retry();
}

​
Getting Help

If you’re still experiencing issues:
  1. Check Status Page: status.cloudgeni.ai
  2. Search Documentation: Use the search bar above
  3. Contact Support: support@cloudgeni.ai
  4. Community: Join our Slack community
When contacting support, please include:
  • Organization ID
  • Reproduction steps
  • Error messages or screenshots
  • Relevant timestamps

Connection Issues

Git and cloud connection troubleshooting

API Authentication

API key setup and usage

FAQ

Frequently asked questions

Static Analysis

Understanding scan results