Prisma · runtime error · P2024

P2024: Timed out fetching a new connection from the connection pool

PrismaClientKnownRequestError: Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)

What it means

Every connection Prisma may open is busy, or the database refused more. In Next.js this is almost always too many PrismaClient instances, or serverless functions each holding their own pool.

Common causes

• new PrismaClient() in many files, or inside a request handler
• next dev hot reload creating a fresh client on every change (no globalThis singleton)
• Serverless functions connecting straight to Postgres instead of through a pooler

How to fix it

1. Create PrismaClient once in lib/db.ts with the globalThis pattern and import db everywhere
2. On serverless, use the provider's pooled connection string (Supabase port 6543 with ?pgbouncer=true, or Neon's -pooler host)
3. Use a direct (non-pooled) URL as directUrl in schema.prisma, for migrations

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL") // pooled
  directUrl = env("DIRECT_URL")   // direct, used by migrate
}

Prompt for Cursor or Claude Code

Prisma throws P2024 (connection pool timeout). Search the codebase for every new PrismaClient(), replace them with one globalThis singleton in lib/db.ts, and tell me whether DATABASE_URL is a pooled connection. If it isn't, show me the schema.prisma change for url + directUrl.

Not quite your error? Paste yours into the free VibeBoot Doctor or browse the Prisma error fixer.