Database Connection Troubleshooting
Connectivity, pool, schema, query, and transaction symptoms.
Separate network reachability, credentials, schema version, pool exhaustion, and data-level errors.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Prisma is shared by API and worker. Use health/log evidence and migration status; map P2002 to conflict and P2025 to not-found rather than treating all database errors as outages.
| Check | Source-backed expectation |
|---|---|
| Scope | Do not reset, drop, or force-sync a shared database to resolve an uncertain connection problem. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm db:validate |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
pnpm db:validate
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.