Troubleshooting common issues

Solutions to common problems and answers to frequently asked questions

Here's how to diagnose and fix common issues with CodeReviewr.

#Reviews aren't triggering

Check these first:

  1. GitHub App installation: Go to Settings. Is the GitHub App installed?
  2. Repository access: In GitHub, check App installation settings. Is the repository included?
  3. Credits: Check your workspace dashboard. Do you have credits remaining?
  4. Webhook delivery: In GitHub, go to Settings → Webhooks. Is the CodeReviewr webhook configured and delivering successfully?

If installation looks correct:

  • Draft PRs: CodeReviewr doesn't review draft PRs by default. Convert to ready for review.
  • Large PRs: PRs over 300KB are skipped. CodeReviewr posts a comment explaining this. Split your PR into smaller chunks.
  • Branch protection: Some branch protection rules can interfere with webhook delivery.

Still not working? Check the workspace dashboard for error logs. Failed reviews show up there with error messages.

#Reviews are slow

Normal delays:

  • Large PRs take 1-3 minutes
  • Complex code requiring extensive context takes longer
  • During peak usage, there can be 30-60 second delays

Unusual delays: If reviews consistently take 5+ minutes for small PRs, check the dashboard for queue status. If all reviews are slow, it might be a system-wide issue.

#Issues aren't posted to GitHub

Common causes:

  • GitHub permissions: The App might not have permission to post comments. Re-install the GitHub App and ensure all permissions are granted.
  • PR is locked: Some repos lock PRs from external comments. Check PR settings.
  • Branch protection: Comments might be blocked by branch protection rules.

Check the dashboard: Look at the review details. Does it show issues found but you don't see comments? Error logs explain why.

#Unexpected costs

Why this happens:

  • Many files accessed: If the AI needs to read many files for context, costs increase. Check the File Reads section in your dashboard.
  • Large diffs: 1000+ line changes naturally cost more than 50-line changes.
  • Complex code: Densely complex code takes more processing to analyze.

How to investigate: Open your workspace dashboard, click on an expensive review, and check what files were accessed. Look at file sizes—were large files read unnecessarily?

Optimization tips: Split large PRs into smaller ones, improve code organization so context is easier to understand, or accept that some code patterns naturally require more context.

If a review costs more than expected, contact support with the PR link.

#Duplicate issues

CodeReviewr tracks issues and marks them solved when fixed. If you're seeing duplicates, check if they're actually the same (same file, same line, same description). If line numbers shifted, they're different issues.

When commits are force-pushed or rebased, incremental reviews can sometimes get confused. If you see exact duplicates (same issue ID reported twice), that's a bug—contact support.

#Credits not showing up

Check these:

  1. Payment completed: Was Stripe payment successful? Check your email for payment confirmation.
  2. Correct workspace: Did you purchase credits for the right workspace? Credits are workspace-specific.
  3. Page refresh: Try refreshing the dashboard. Credits usually appear within seconds.

If credits still missing: Contact support with your Stripe receipt or transaction ID.

#Review quality issues

CodeReviewr uses AI, which isn't perfect:

  • False positives: Sometimes the AI flags things that aren't actually problems. Treat AI reviews as helpful suggestions, not authoritative verdicts.
  • Missed issues: Sometimes obvious bugs aren't caught. AI isn't a replacement for human review, it's a supplement.
  • Context confusion: If your codebase has unusual patterns, the AI might misunderstand and suggest wrong fixes.

What you can do: Provide more context in PR descriptions, keep PRs focused, and report quality issues through the contact form. We continuously improve based on feedback.

AI code review catches most issues, but not 100%. Use it as a first pass, then add human review for critical code paths.

#Getting help

If none of these solutions work, check your workspace dashboard for error logs and review details. You can also check GitHub for webhook delivery status and App permissions.

Contact support through the contact form on the website. Include workspace ID, PR link if applicable, error messages, and steps to reproduce. We respond to every support request, usually within 24 hours.