Troubleshooting
Solutions to common issues you might encounter with Jasper.
Reviews Not Appearing
Check GitHub App Installation
Ensure Jasper is installed and has access to the repository:
- Go to your GitHub organization settings
- Click Installed GitHub Apps
- Find Jasper and click Configure
- Verify the repository is in the selected list
Check Repository Settings
Verify automatic reviews are enabled:
- Go to the Jasper dashboard
- Navigate to the repository settings
- Ensure "Automatic Reviews" is enabled
Check Credits
Reviews require credits. Check your organization's credit balance in the dashboard. If you've run out, purchase more credits.
@jasper Not Responding
Verify Mention Format
Make sure you're using the correct format:
@jasperfollowed by your question- Or
/jasper commandfor slash commands
Check for Bot User
Jasper won't respond to its own comments or other bot accounts to prevent loops.
Wait for Processing
Responses typically take 30-60 seconds. Large PRs may take longer.
Slow Reviews
Review time depends on:
- PR size - Larger diffs take longer to analyze
- File count - More files = more processing time
- Queue depth - During peak times, reviews may queue
Most reviews complete within 1-3 minutes. Contact support if reviews consistently take longer than 5 minutes.
Incorrect or Unhelpful Reviews
Provide Feedback
If Jasper's suggestions seem off, reply to the comment with context. The AI learns from your project's patterns over time.
File Filters
Exclude generated files, vendored code, or other files that shouldn't be reviewed using file filters in repository settings.
Authentication Issues
Can't Sign In
- Ensure you're using the correct GitHub account
- Check that you're a member of an organization with Jasper installed
- Try signing out of GitHub and signing back in
Missing Repositories
Repositories sync from GitHub periodically. Click "Sync Repositories" in the dashboard to trigger an immediate sync.
Error Codes Reference
Common error codes and their meanings:
| Code | Message | Solution |
|---|---|---|
AUTH_001 |
GitHub authentication failed | Re-authenticate by signing out and back in |
AUTH_002 |
Organization access denied | Request access from your organization admin |
AUTH_003 |
Token expired | Refresh the page to get a new session token |
REVIEW_001 |
Insufficient credits | Purchase more credits or wait for monthly reset |
REVIEW_002 |
Repository not found | Sync repositories or check GitHub App permissions |
REVIEW_003 |
PR diff too large | Split the PR into smaller changes |
REVIEW_004 |
Review timeout | Retry the review; large PRs may need multiple attempts |
WEBHOOK_001 |
Webhook delivery failed | Check webhook URL and server availability |
WEBHOOK_002 |
Invalid webhook signature | Verify webhook secret matches in settings |
API_001 |
Invalid API token | Generate a new API token in settings |
API_002 |
Insufficient scope | Create token with required scopes |
SYNC_001 |
GitHub sync failed | Check GitHub status; retry in a few minutes |
Rate Limiting
Jasper enforces rate limits to ensure fair usage and system stability.
Rate Limit Tiers
| Endpoint Type | Limit | Window |
|---|---|---|
| API requests (authenticated) | 120 requests | Per minute |
| API requests (unauthenticated) | 60 requests | Per minute |
| Code reviews | Based on credits | N/A |
| Webhook deliveries | 1000 per endpoint | Per hour |
| Desktop app | 10000 requests | Per minute |
Rate Limit Headers
API responses include rate limit information:
X-RateLimit-Limit— Maximum requests allowedX-RateLimit-Remaining— Requests remaining in windowX-RateLimit-Reset— Unix timestamp when limit resets
When Rate Limited
If you exceed rate limits:
- You'll receive a
429 Too Many Requestsresponse - Wait for the reset time before retrying
- Implement exponential backoff in your integrations
Performance Optimization
Tips to get the best performance from Jasper.
Faster Reviews
- Keep PRs small — PRs under 500 lines review fastest
- Exclude generated files — Use file filters to skip build artifacts
- Exclude vendor code — Filter out node_modules, vendor/, etc.
- Use .jasperignore — Create a file listing paths to skip
Reducing Credit Usage
- Filter file types — Only review code files you care about
- Disable for draft PRs — Save credits until PR is ready
- Set minimum diff size — Skip reviews for trivial changes
- Use local CLI — Review locally before pushing
Dashboard Performance
- Use fewer widgets — More widgets = slower load times
- Increase refresh interval — Reduce auto-refresh frequency
- Use the Minimal template — Optimized for speed
- Clear browser cache — If dashboard feels sluggish
API Integration Performance
- Use webhooks — Instead of polling for changes
- Cache responses — Many endpoints return cacheable data
- Batch requests — Use bulk endpoints where available
- Use pagination — Don't fetch more data than needed
Browser Compatibility
Jasper works best with modern browsers:
| Browser | Minimum Version |
|---|---|
| Chrome | 90+ |
| Firefox | 88+ |
| Safari | 14+ |
| Edge | 90+ |
Known Browser Issues
- Safari Private Mode — Some features may not work due to storage restrictions
- Ad blockers — May interfere with analytics and some API calls
- VPN/Proxy — May cause WebSocket connection issues for real-time features
Network Issues
WebSocket Connection Failed
Real-time features (Messenger, notifications) use WebSockets:
- Check if your firewall allows WebSocket connections
- Try refreshing the page
- Check if you're behind a proxy that blocks WebSockets
- Features will fall back to polling if WebSockets fail
Slow Loading
- Check your internet connection speed
- Try a different network (mobile hotspot vs WiFi)
- Clear browser cache and cookies
- Disable browser extensions temporarily
Contact Support
If you're still having issues:
- Email: [email protected]
- Include your organization name and specific error messages
- Provide browser console logs if available (F12 → Console)
- Note the approximate time the issue occurred
Before Contacting Support: Check our status page for any ongoing incidents that may be affecting your experience.