Troubleshooting¶
This section helps you diagnose and resolve common issues with Mayo ASPM. Each guide covers symptoms, causes, and solutions.
Guides¶
| Guide | Covers |
|---|---|
| Scanning issues | Scan stuck, clone fails, timeout, no findings |
| PR scanning issues | No comment posted, check run missing, wrong branch |
| Policy issues | Validation errors, no effect, wrong output |
| Integration issues | GitHub App, Jira connection, API keys |
| Common error messages | Error messages and their solutions |
General troubleshooting steps¶
Before diving into specific guides, try these steps:
1. Check integration health¶
Navigate to Settings > Integrations and verify all integrations show Connected status.
2. Check the audit log¶
Navigate to Settings > Audit Log for recent events. Error events are highlighted in red.
3. Check scan status¶
Navigate to Scans and look for failed or stuck scans. Click a scan to see detailed logs.
4. Verify permissions¶
Ensure your account role has the necessary permissions for the action you're trying to perform.
Quick reference¶
| Symptom | Likely cause | Guide |
|---|---|---|
| Scan shows "Queued" for > 10 min | Queue backlog or scan limit | Scanning |
| No findings after scan | Scanner misconfiguration or empty repo | Scanning |
| PR has no check run | GitHub App permissions or webhook issue | PR scanning |
| Policy not affecting findings | Policy inactive or scoping issue | Policies |
| "Unauthorized" API errors | Expired or revoked API key | Integrations |
| Jira tickets not syncing | Webhook deleted or connection expired | Integrations |
Getting support¶
If the troubleshooting guides don't resolve your issue:
- Check the status page at status.mayoaspm.com for known outages.
- Contact support at support@mayoaspm.com with:
- Your organization ID (found in Settings > Organization)
- The request ID from any error response (
X-Request-IDheader) - Steps to reproduce the issue
- Screenshots if applicable