Troubleshooting

Error: "Invalid API key" or "Unauthorized"

Causes:

• API key not set in GitHub Secrets
• Incorrect secret name (must be exactly RSOLV_API_KEY)
• API key was revoked or expired
• Typo in API key value

Solutions:

1. Verify secret name in Settings → Secrets → Actions is exactly RSOLV_API_KEY
2. Check your API key at rsolv.dev/dashboard
3. Generate a new API key if needed and update the secret
4. Ensure no extra spaces or characters in the secret value

Workflow doesn't appear in Actions tab

Causes:

• Workflow file not in correct location
• YAML syntax errors
• File not committed to repository
• GitHub Actions disabled for repository

Solutions:

1. Verify file is at .github/workflows/rsolv-security.yml
2. Use a YAML validator to check syntax: yamllint.com
3. Ensure file is committed and pushed to GitHub
4. Check Settings → Actions → General to enable GitHub Actions
5. Verify the on: trigger matches your use case (push, pull_request, etc.)

Scan completes but no issues appear

This might be good news! It could mean:

• No vulnerabilities detected (secure code!)
• False positives were filtered out by AST validation
• Scanned files don't match supported languages

To verify:

1. Check workflow logs in Actions tab for scan results summary
2. Verify your repository contains supported languages (JavaScript, TypeScript, Python, Ruby, PHP, Java)
3. Test with a known vulnerable repository to confirm RSOLV is working
4. Check if issues permission is granted in workflow file

Error: "Rate limit exceeded"

What it means:

RSOLV has rate limits to ensure fair usage and system stability. The AST validation API allows 500 requests per hour per API key.

Solutions:

1. Wait for the rate limit window to reset (shown in error message)
2. Reduce scan frequency (e.g., weekly instead of on every push)
3. Use max_issues parameter to limit processing
4. Contact support@rsolv.dev for enterprise rate limits

Error: "Resource not accessible by integration"

Causes:

• Missing or insufficient permissions in workflow file
• Organization-level restrictions on GitHub Actions

Solutions:

1. Add required permissions to your workflow file:

permissions:
  contents: write      # For creating commits
  issues: write        # For creating issues
  pull-requests: write # For creating PRs

2. Check organization settings: Settings → Actions → General
3. Ensure "Allow GitHub Actions to create and approve pull requests" is enabled

Workflow times out or takes too long

Causes:

• Large repository with many files to scan
• Running all three phases (scan, validate, mitigate) in one job
• Network latency to RSOLV API

Solutions:

1. Use separate jobs for each phase (see workflow templates)
2. Limit processing with max_issues: '3' parameter
3. Use mode: 'scan' first to identify issues, then process incrementally
4. Increase GitHub Actions timeout (default is 6 hours, rarely needed)

Validate phase fails to generate tests

Causes:

• Test framework not detected or unsupported
• Complex codebase structure
• Missing test dependencies

Solutions:

1. Ensure your project has a supported test framework (Jest, RSpec, pytest, PHPUnit, JUnit)
2. Check workflow logs for specific error messages
3. Verify test dependencies are installed in your repository
4. Contact support@rsolv.dev with repository details for assistance

Mitigate phase fails to create pull request

Causes:

• Missing pull-requests: write permission
• Branch protection rules preventing automatic PRs
• PR already exists for the fix

Solutions:

1. Add pull-requests: write to permissions section
2. Check Settings → Branches for protection rules that may block PRs
3. Review existing PRs - RSOLV won't create duplicates
4. Check workflow logs for specific error messages