We have an issue with Connection Pool timout. We can’t figure out whats causing the connection pool limit to get filled up and exhaust the connection pool queue. This leads to connection pool timeouts. Tried to use the built in prisma logger but there is no way to log which query is failing when timeout is happening. Preferably there should be a query parameter in this errorobject.

}

meta: { connection_limit: 9 }

clientVersion: '2.29.1',

code: 'P2024',

at processTicksAndRejections (internal/process/task_queues.js:97:5) {

at runMicrotasks (<anonymous>)

at RequestHandler.request (/app/node_modules/@prisma/client/runtime/index.js:36744:15)

PrismaClientKnownRequestError3 [PrismaClientKnownRequestError]: Timed out fetching a new connection from the connection pool. (More info: <http://pris.ly/d/connection-pool>, Current connection limit: 9)

}