P
Prisma5mo ago
Ted

Get P6004 and P5000 error running Vercel production query through Accelerate

I receive this error and I don't understand the cause is. The query is straightforward, performing a fetch of 25 rows with a JOIN, no filtering or sorting, that should reply fast with a small handful of columns to populate a MUI DataGridPro React component. This works via Preview and localhost. Accelerate status appears fine today, but not sure about Cloudflare. I hope someone can give me a clue or how to more quickly debug this and get me on track to resolve ASAP. I'm not sure why this is timing out.
PrismaClientKnownRequestError:
Invalid `prisma.$queryRawUnsafe()` invocation:
This request could not be understood by the server: {"type":"UnknownJsonError","body":{"code":"P6004","message":"The Query did not produce a result within the maximum allowed execution time of 10 seconds."}} (The request id was: 89b23bb50aecb477)
at In.handleRequestError (/var/task/node_modules/.prisma/client/runtime/library.js:122:6877)
at In.handleAndLogRequestError (/var/task/node_modules/.prisma/client/runtime/library.js:122:6211)
at In.request (/var/task/node_modules/.prisma/client/runtime/library.js:122:5919)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async l (/var/task/node_modules/.prisma/client/runtime/library.js:127:11167)
at async P (/var/task/apps/frontend/.next/server/chunks/7842.js:390:44)
at async p (/var/task/apps/frontend/.next/server/app/api/v1/offertargets/route.js:1:1615)
at async /var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:34666
at async eS.execute (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:25813)
at async eS.handle (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:35920) {
code: 'P5000',
clientVersion: '5.14.0',
meta: undefined
}
PrismaClientKnownRequestError:
Invalid `prisma.$queryRawUnsafe()` invocation:
This request could not be understood by the server: {"type":"UnknownJsonError","body":{"code":"P6004","message":"The Query did not produce a result within the maximum allowed execution time of 10 seconds."}} (The request id was: 89b23bb50aecb477)
at In.handleRequestError (/var/task/node_modules/.prisma/client/runtime/library.js:122:6877)
at In.handleAndLogRequestError (/var/task/node_modules/.prisma/client/runtime/library.js:122:6211)
at In.request (/var/task/node_modules/.prisma/client/runtime/library.js:122:5919)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async l (/var/task/node_modules/.prisma/client/runtime/library.js:127:11167)
at async P (/var/task/apps/frontend/.next/server/chunks/7842.js:390:44)
at async p (/var/task/apps/frontend/.next/server/app/api/v1/offertargets/route.js:1:1615)
at async /var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:34666
at async eS.execute (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:25813)
at async eS.handle (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:35920) {
code: 'P5000',
clientVersion: '5.14.0',
meta: undefined
}
1 Reply
Ted
TedOP5mo ago
I'd like to trying bypassing Accelerate on production as a test, but not sure how to qucikly extract Prisma Accelerate without extensive changes or updating the schema.
Want results from more Discord servers?
Add your server