ShipGauge

Troubleshooting

Fix empty Overview, gate failures, and common API errors

No events on Overview

  1. Confirm SHIPGAUGE_API_KEY / SHIPGAUGE_PROJECT_ID / baseUrl.
  2. Hit ingest with curl (Ingest API) to isolate SDK issues.
  3. Check the browser network tab for 401 / 402 / 403 / 429.
  4. Ensure the dashboard env filter matches the event environment (aliases like prod ↔ production count as the same). If you omit environment, events land in production.

Gate always fails

  1. Read the PR comment / check summary for which rule failed.
  2. Compare suite name to .shipgauge/gate.yml.
  3. Re-run with the same suite locally.
  4. If you intentionally changed cost/quality, re-baseline deliberately.
  5. See CI Gate and GitHub Gate.

HTTP status cheat sheet

StatusLikely causeDoc
401Bad/revoked keyIngest API
402Monthly quotaLimits
403Org suspendedContact support / workspace admin
429Hard budget or ingest rate limitBudgets
503Temporary platform disableRetry 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.

Next