Skip to main content
Resolve common issues when connecting or using your Blitzy integrations.
Jump to: GitHub | Azure DevOps | GitLab | Getting Help

​
GitHub Issues

  • Repository not appearing - Ensure you’ve granted access through GitHub Settings > Applications > Blitzy
  • Permission denied errors - Verify the Blitzy app has the required permissions
  • Organization access - Organization owners may need to approve the app

​
Azure DevOps Issues

  • Project not visible - Confirm you have access to the project and have granted Blitzy access
  • Authentication errors - Try disconnecting and reconnecting the integration
  • Service connection issues - Check Azure DevOps project settings for service connection requirements

​
GitLab Troubleshooting

For detailed information about GitLab’s API and authentication, see GitLab REST API Documentation.
Quick Diagnosis: Jump directly to your issue:

​
OAuth & Authentication

Error message:
{
  "error": "access_denied",
  "error_description": "The resource owner or authorization server denied the request"
}
The user clicked “Deny” or cancelled the OAuth authorization flow in GitLab.Reference: GitLab OAuth 2.0 API
Error message:
Could not authenticate you from OpenIDConnect because 'Invalid 'state' parameter'
The OAuth state parameter verification failed. This is a security measure to prevent CSRF attacks. Common causes include expired state (>10 minutes), browser back button usage, or session/cookie issues.Reference: GitLab OAuth 2.0 API
Error message:
{
  "error": "invalid_token",
  "error_description": "Token is expired. You can either do re-authorization or token refresh."
}
The access token has expired. From GitLab 16.0, all access tokens have an expiration date.Reference: GitLab Token Troubleshooting

​
Permission & Access

Error message:
The request requires higher privileges than provided by the access token
The OAuth access token doesn’t have the required scope for the requested operation.Required scopes for integrations:
  • api - Full API access
  • read_api - Read access to groups and projects
  • write_repository - Create branches and commits
  • read_user - User information access
Reference: GitLab REST API Authentication

​
Rate Limits

Error message:
Retry later
(Plain text response with 429 status code)You’ve exceeded GitLab’s rate limits. GitLab.com limits are:
  • Unauthenticated requests - 500 requests/minute per IP
  • Authenticated requests - 2000 requests/minute per user
The response includes a Retry-After header indicating when to retry.References:

​
Getting Help

For issues not covered above, consult the official GitLab documentation: For Blitzy-specific integration issues, email [email protected] with:
  • Exact GitLab error message and status code
  • Screenshot of the error
  • GitLab Cloud or Self-Managed (with version if Self-Managed)
  • Your GitLab role in the namespace
  • When the error occurs (during setup, runtime, etc.)