ShipWright help
Troubleshooting
Common staging and pilot-test issues for auth, migrations, dispatch, payments, and route proof.
What this screen does
- Gives operators a short checklist for the most common staging failures.
- Keeps proof-of-flow debugging grounded in API, database, and browser evidence.
- Separates real blockers from browser noise.
What to do next
- Start with health and readiness.
- Confirm migrations and environment variables before debugging UI state.
- Verify downstream records after every paid-delivery proof.
Status meanings
StatusMeaningNext action
healthz 200The API process is alive.Check readiness next.
readyz 200Critical schema checks pass.Run authenticated smoke or proof.
no_eligible_driversDispatch could not find a suitable staged driver.Fix driver fixture then retry dispatch.
stripe_not_configuredStripe env is missing or not deployed.Set env vars and redeploy API/web.
Related guidance
Operator actions
- Check /healthz first for process liveness.
- Check /readyz next for critical schema compatibility.
- Run the staging smoke/proof commands when credentials are available.
- Use Render logs for API exceptions and Supabase for record integrity proof.
Common problems
- API timeout on /v1/business/context: check Render health, readiness, and auth token freshness.
- 500 after deployment: confirm migrations are applied to staging Supabase and /readyz passes.
- No offers after paid order: verify staged driver fixture, online availability, vehicle type, and proximity.
- RSC payload fetch fallback: refresh the route and check whether the deployed web build changed while the browser tab was open.
- Duplicate order concern: retry with the same idempotency key and verify the same downstream records are reused.