Evaluator Troubleshooting
This page covers the issues buyers hit most often while evaluating the starter locally.
It is intentionally shorter than the maintainer troubleshooting docs. The goal here is to get an evaluator unstuck fast.
Setup Does Not Finish Cleanly
If pnpm continu:init stalls or reports that Convex is not configured, finish the Convex setup flow first, then rerun the command.
The starter assumes Convex linking is part of first-run setup.
The App Starts But Tenant Routing Does Not Work
If the main app loads at localhost:3001 but tenant hosts do not resolve, check the local subdomain setup and confirm you are using *.localhost for tenant routes.
The tenant path is part of the actual product model, so local host resolution matters during evaluation.
Convex Types Or Generated Refs Look Wrong
If type errors appear after backend or schema changes, rerun the backend dev process so Convex regenerates types.
Billing Webhooks Fail During Evaluation
If Polar webhook calls are rejected, the most common issue is a mismatched POLAR_WEBHOOK_SECRET.
Tenant Data Looks Missing Or Crossed
If tenant-scoped data does not look right, the first thing to suspect is tenant scoping rather than the UI.
The starter expects tenant data to stay isolated by organization boundary.
What To Use For Deeper Debugging
- Convex logs for backend execution issues
- Next.js server output for app/runtime issues
- browser console for client-side failures
If you need deeper maintainer-level debugging notes, continue into docs/dev.