Migration Troubleshooting
Pending, failed, interrupted, and rollback-sensitive migrations.
Record migration identity and database backup state before taking action.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Deployment uses controlled migration application and verification. An application rollback may not reverse a schema migration; choose between forward repair, restore, or release rollback with explicit ownership.
| Check | Source-backed expectation |
|---|---|
| Scope | Never run a destructive migration reset outside an approved disposable local target. |
| 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.