API Startup Troubleshooting
Nest bootstrap, module wiring, dependency, and compiled-artifact failures.
Check build output, environment validation, module initialization, and dependency status in that order.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The API depends on ConfigModule, Prisma, Redis-backed services, Meilisearch seams, global guards, and provider registries. A startup failure can be compile-time, DI-time, configuration-time, or connection-time.
| Check | Source-backed expectation |
|---|---|
| Scope | Do not patch production code or disable guards as a runtime workaround. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm --filter @autocore/api build |
| 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 --filter @autocore/api build
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.