Troubleshooting
Fix empty Overview, gate failures, and common API errors
No events on Overview
- Confirm
SHIPGAUGE_API_KEY/SHIPGAUGE_PROJECT_ID/baseUrl. - Hit ingest with curl (Ingest API) to isolate SDK issues.
- Check the browser network tab for
401/402/403/429. - Ensure the dashboard env filter matches the event
environment(aliases likeprod↔productioncount as the same). If you omitenvironment, events land in production.
Gate always fails
- Read the PR comment / check summary for which rule failed.
- Compare suite name to
.shipgauge/gate.yml. - Re-run with the same suite locally.
- If you intentionally changed cost/quality, re-baseline deliberately.
- See CI Gate and GitHub Gate.
HTTP status cheat sheet
| Status | Likely cause | Doc |
|---|---|---|
401 | Bad/revoked key | Ingest API |
402 | Monthly quota | Limits |
403 | Org suspended | Contact support / workspace admin |
429 | Hard budget or ingest rate limit | Budgets |
503 | Temporary platform disable | Retry later |
GitHub check missing
- Workflow needs
checks: write - Check name must be ShipGauge Gate
- Run the workflow once before adding required checks
SSO loop / no button
- Domain allowlist and Team plan — Enterprise SSO
- Callback URL must match production origin exactly
Still stuck
Email support with: project id, approximate timestamp, request id / status code, and whether the failing path is SDK, curl, or CI.