Troubleshooting

This guide helps resolve common issues when working with Prisma Postgres.

Running the following command fails because the --db option is not recognized:

bunx --bun prisma init --db

pnpm prisma init --db

yarn prisma init --db

npx prisma init --db

This can occur due to npx caching. If you've previously run npx prisma init, your machine may be using an outdated cached version that doesn't recognize the --db flag because it was only introduced in a later version of Prisma ORM.

Explicitly run the Prisma ORM 7 CLI through its prev dist-tag:

bunx --bun prisma@prev init --db

pnpm dlx prisma@prev init --db

yarn dlx prisma@prev init --db

npx prisma@prev init --db

This runs the latest Prisma ORM 7 CLI, which supports the flag, preventing issues with outdated command syntax.

When running the command:

bunx --bun prisma@prev init --db

pnpm dlx prisma@prev init --db

yarn dlx prisma@prev init --db

npx prisma@prev init --db

You may encounter the following error message in your logs:

Workspace plan limit reached for feature "Project".

Your default workspace project limit has been reached.

To resolve this issue, consider the following options:

• Configure a different Workspace as your default, one that has available capacity for additional projects.
• Delete unused projects or databases from your current default Workspace to free up space.
• Ensure that you are logged into the correct account in the Prisma CLI. For more details on authentication and account management, please refer to the Prisma CLI documentation.
• Upgrade to a plan that supports more projects in your default Workspace.