Error code

PARTS_MIGRATE_AFTER_MAIN

1 minute to read

What it means. The main part goes live and is checked before another part runs its migrations, so on the first deploy its home page meets a database with no tables yet.

What to do. Nothing to do: if the main part's first check fails, the deploy carries on with the other parts and deploys the main part again after them. To save that second build, make its home page answer while the tables do not exist yet (a short "being set up" page rather than an error). This is a warning; deploy continues.

HTTP status: 422
Retryable after applying the fix: yes

Every failure from the CLI or an MCP tool has this shape:

JSON

{
  "ok": false,
  "code": "PARTS_MIGRATE_AFTER_MAIN",
  "message": "The main part goes live and is checked before another part runs its migrations, so on the first deploy its home page meets a database with no tables yet.",
  "fix": "Nothing to do: if the main part's first check fails, the deploy carries on with the other parts and deploys the main part again after them. To save that second build, make its home page answer while the tables do not exist yet (a short \"being set up\" page rather than an error). This is a warning; deploy continues.",
  "file": "<where to edit, when known>",
  "retryable": true,
  "docs": "https://docs.uarpie.app/errors/PARTS_MIGRATE_AFTER_MAIN"
}

Apply fix (edit file when it is given), then run the same command again.

This page as Markdown: /docs/errors/PARTS_MIGRATE_AFTER_MAIN.mdllms.txt