CLIError codes
NEXTLY_MIGRATION_SNAPSHOT_MISSING
`nextly migrate:resolve --applied` has no snapshot to compare the live schema with.
Cause
nextly migrate:resolve --applied has no snapshot to compare the live schema with.
nextly migrate:resolve --applied records a file as applied only once the live schema matches the snapshot migrate:create wrote beside it in meta/. The file has no snapshot, so there is nothing to compare against.
Fix
- Restore the snapshot from version control if it was deleted, then run the command again.
- If the file never had one, such as a hand-written migration, and you know its statements have run, re-run with
--skip-verify.
Example
✗ No paired snapshot for 20261020_120000_add_posts.sql; cannot verify.
Why: `--applied` records a file once the live schema matches the snapshot `migrate:create` wrote beside it in `meta/`, and this file has none.
Next: Re-run with --skip-verify to override.
Docs: https://nextlyhq.com/docs/cli/errors/nextly-migration-snapshot-missing (NEXTLY_MIGRATION_SNAPSHOT_MISSING)NEXTLY_MIGRATION_PARTIALLY_APPLIED
A migration that runs outside a transaction failed part-way, now or in its newest attempt, and the statements before the failure stayed applied.
NEXTLY_PERMISSION_COLLISION
A plugin's custom permission repeats another, targets a resource Nextly reserves, or repeats one Nextly creates itself.