How to fix P1008: Operations timed out in Prisma

What this error means

The P1008 error indicates that your Prisma Client attempted to execute a database operation but the operation did not complete within the configured timeout period. This timeout can occur at different stages: when establishing a connection to the database, when executing a query, or when fetching a new connection from the connection pool. Prisma manages a client-side connection pool that maintains connections to your database. When all connections are in use and a new query arrives, it waits in a queue for an available connection. If no connection becomes available within the pool timeout (default 10 seconds), P1008 is thrown. The actual cause depends on your setup: the database may be slow due to resource constraints, long-running queries may hold connections hostage, or the pool size may be too small for your workload.

Typical symptoms

• Queries fail with error code P1008 after application has been running for a while
• Random timeout failures on database operations, especially under load
• All subsequent queries fail after one timeout, requiring application restart
• Migrations fail with P1008 during `prisma migrate deploy` or `prisma db push`
• Serverless functions experience frequent timeouts that clear on retry
• Error message includes connection pool timeout details: 'Timed out fetching a new connection from the connection pool'

Common causes

1. Connection pool timeout is too short for your workload (default 10 seconds is insufficient for slow queries)
2. Database is overloaded or has limited resources, causing queries to execute slowly and hold connections longer
3. Connection limit is too low for concurrent usage, causing queue buildup when all connections are busy
4. Long-running queries or transactions hold connections without releasing them, starving other queries
5. Database migration on large tables exceeds the default 5-second connect_timeout during `prisma migrate`
6. Serverless environment has strict cold-start delays or database is in a different geographic region than the function
7. External connection pooler (like PgBouncer) is misconfigured or has its own timeout limits
8. Network latency or firewall rules delay connection establishment beyond the timeout window

How to fix "P1008: Operations timed out"

# For PostgreSQL
psql -h <your-host> -U <your-user> -d <your-db> -c "SELECT 1"

# For MySQL
mysql -h <your-host> -u <your-user> -p <your-db> -e "SELECT 1"

DATABASE_URL="postgresql://user:password@localhost:5432/mydb?connection_limit=10&pool_timeout=20"

DATABASE_URL="postgresql://user:password@localhost:5432/mydb?connect_timeout=30&pool_timeout=20"

DATABASE_URL="postgresql://user:password@localhost:5432/mydb?connection_limit=15&pool_timeout=20"

-- PostgreSQL
SELECT count(*) FROM pg_stat_activity;

-- MySQL
SHOW STATUS WHERE variable_name = 'Threads_connected';

const prisma = new PrismaClient({
  log: ['query'],
});

// Bad: Fetches everything
const user = await prisma.user.findUnique({ where: { id: 1 } });

// Good: Fetches only what you need
const user = await prisma.user.findUnique({
  where: { id: 1 },
  select: { id: true, email: true, name: true },
});

model Post {
  id    Int     @id @default(autoincrement())
  title String
  authorId Int
  author User @relation(fields: [authorId], references: [id])

  @@index([authorId])  // Index for filtering
}

// Bad: N+1 problem
const users = await prisma.user.findMany();
for (const user of users) {
  const posts = await prisma.post.findMany({ where: { authorId: user.id } });
}

// Good: Single query with relations
const users = await prisma.user.findMany({
  include: { posts: true },
});

const results = await prisma.$queryRaw`
  SELECT u.id, u.name, COUNT(p.id) as post_count
  FROM User u
  LEFT JOIN Post p ON u.id = p.authorId
  GROUP BY u.id
`;

DATABASE_URL="postgresql://user:password@localhost:5432/mydb?connect_timeout=30&socket_timeout=30"

# Check migration status
npx prisma migrate status

# If migration shows as failed but changes were applied:
npx prisma migrate resolve --rolled-back "<migration_name>"

# Or mark it as successfully applied:
npx prisma migrate resolve --applied "<migration_name>"

DATABASE_URL="prisma://accelerate.prisma-data.net/?api_key=YOUR_API_KEY"

[databases]
mydb = host=production-db.example.com port=5432 dbname=mydb

[pgbouncer]
pool_mode = transaction
max_client_conn = 1000
default_pool_size = 25

DATABASE_URL="postgresql://user:password@pgbouncer-host:6432/mydb"

// lib/prisma.ts
import { PrismaClient } from "@prisma/client";

const prismaClientSingleton = () => {
  return new PrismaClient();
};

type PrismaClientSingleton = ReturnType<typeof prismaClientSingleton>;

const globalForPrisma = globalThis as unknown as {
  prisma: PrismaClientSingleton | undefined;
};

const prisma = globalForPrisma.prisma ?? prismaClientSingleton();

export default prisma;

if (process.env.NODE_ENV !== "production") globalForPrisma.prisma = prisma;

await prisma.$transaction(
  async (tx) => {
    // Multi-step operation
    await tx.user.update({ where: { id: 1 }, data: { name: "Alice" } });
    await tx.post.create({ data: { title: "New Post", authorId: 1 } });
  },
  {
    timeout: 30000, // 30 seconds (in milliseconds)
  }
);

async function executeWithRetry<T>(
  fn: () => Promise<T>,
  maxRetries: number = 3,
  baseDelay: number = 100
): Promise<T> {
  for (let attempt = 0; attempt < maxRetries; attempt++) {
    try {
      return await fn();
    } catch (error) {
      if (
        attempt === maxRetries - 1 ||
        !String(error).includes("P1008")
      ) {
        throw error;
      }

      const delay = baseDelay * Math.pow(2, attempt);
      await new Promise((resolve) => setTimeout(resolve, delay));
    }
  }
  throw new Error("Max retries exceeded");
}

// Usage:
const user = await executeWithRetry(() =>
  prisma.user.findUnique({ where: { id: 1 } })
);

Advanced notes

-- PostgreSQL: Show active connections
SELECT datname, count(*) FROM pg_stat_activity GROUP BY datname;

-- MySQL: Monitor threads
SHOW STATUS LIKE 'Threads%';

Frequently asked questions

What does "P1008" mean?

The P1008 error indicates that your Prisma Client attempted to execute a database operation but the operation did not complete within the configured timeout period. This timeout can occur at different stages: when establishing a connection to the database, when executing a query, or when fetching a new connection from the connection pool. Prisma manages a client-side connection pool that maintains connections to your database.

How do I fix "P1008"?

P1008 occurs when Prisma Client cannot complete database operations within the connection timeout window, typically caused by database overload, pool exhaustion, or slow queries. Solutions involve adjusting timeout settings, optimizing queries, or managing connection pools.

What causes "P1008"?

Connection pool timeout is too short for your workload (default 10 seconds is insufficient for slow queries) Database is overloaded or has limited resources, causing queries to execute slowly and hold connections longer Connection limit is too low for concurrent usage, causing queue buildup when all connections are busy

Is the "P1008" error serious?

Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Related errors

• P1009: Database `{database_name}` already exists on the database server at `{database_host}:{database_port}`

  How to fix "P1009: Database already exists" in Prisma

  MEDIUM

• P1003: Database does not exist

  How to fix "P1003: Database does not exist" in Prisma

  MEDIUM

• P1010: User was denied access on the database

  How to fix "P1010: User was denied access on the database" in Prisma

  HIGH

• P1002: The database server was reached but timed out

  Database server was reached but timed out

  HIGH

• P1013: The provided database string is invalid

  The provided database string is invalid

  HIGH

• P2022: The column `{column}` does not exist in the current database.

  The column does not exist in the current database

  HIGH

Official resources & further reading

• 📚Prisma Official Documentation
• 📖
  Prisma Documentation: Error Reference(Official Docs)
• 📖
  Prisma Documentation: Connection Pool(Official Docs)
• 📖
  Prisma Documentation: Troubleshooting Connection Timeouts(Official Docs)
• 🐙
  GitHub: P1008 Operations timed out after 30s(GitHub)
• 🐙
  GitHub: Connection pool timeout discussion(GitHub)
• 📖
  Prisma Documentation: Connection Pooling for PostgreSQL(Official Docs)