Signal Sapien
The back office tables do not exist yet
The panel is running against a database that has not had the back office migration applied.

This is expected if the panel was deployed before the console shipped the migration. The panel applies none of its own — the console's deploy owns the schema, so a back office can never migrate the database out from under the product.

The missing migration

prisma/migrations/20260811000000_admin_panel

Apply it, in order of preference

  1. Deploy the console from a branch that contains it. Its entrypoint runs prisma migrate deploy at startup unless RUN_MIGRATIONS=false.
  2. Or run the schema tooling image against the same database:docker run --rm --network <network> -e DATABASE_URL="…" \
      ghcr.io/<owner>/<repo>:<tag>-tools \
      npx prisma migrate deploy    The tag has to be one built after the migration landed, or the folder is not in the image.

This page rechecks on every request. Once the tables exist it goes away on its own — no redeploy of the panel needed.