PROMOTE_COLLECTION_NOT_FOUND

`db:sync --promote` names a collection the Schema Builder has no record of.

Cause

db:sync --promote names a collection the Schema Builder has no record of.

nextly db:sync --promote <slug> moves a collection built in the Schema Builder into nextly.config.ts. No collection the Schema Builder created has this slug.

Fix

Check the slug in the admin's Schema Builder.
A collection already defined in nextly.config.ts is in code and needs no promotion.

Example

✗ Collection 'posts' not found in UI source (dynamic_collections).
  Why:  `--promote` moves a collection built in the Schema Builder into code, and no collection with this slug was built there.
  Next: Check the slug in the admin's Schema Builder. A collection already defined in `nextly.config.ts` is in code and needs no promotion.
  Docs: https://nextlyhq.com/docs/cli/errors/promote-collection-not-found  (PROMOTE_COLLECTION_NOT_FOUND)

PROJECT_ALREADY_INITIALIZED

The folder already has a `nextly.config.ts`, so `nextly init` did not overwrite it.

REFUSED_STATEMENT

A migration holds a statement the runner refuses to run where it is, so nothing in it ran.

PROMOTE_COLLECTION_NOT_FOUND

Cause

Fix

Example

On this page