UnknownJsonError - P6000 - Something went wrong
Hello,
I get a strange error using prisma accelerate. What could be the cause?
Unknown server error: {"type":"UnknownJsonError","body":{"code":"P6000","message":"Something went wrong."}} (The request id was: 8e16bac8eee93b72)
at Yr.handleRequestError (/var/task/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/edge.js:20:7527)
at Yr.handleAndLogRequestError (/var/task/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/edge.js:20:6835)
at Yr.request (/var/task/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/edge.js:20:6525)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async l (/var/task/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/edge.js:29:9558)
at async N (/var/task/.next/server/chunks/8539.js:1:5647)
at async /var/task/.next/server/app/api/v1/stays/overview/route.js:1:1650
at async Promise.all (index 29)
at async v (/var/task/.next/server/app/api/v1/stays/overview/route.js:1:1596)
at async g (/var/task/.next/server/app/api/v1/stays/overview/route.js:1:2086) {
code: 'P5006',
clientVersion: '5.22.0',
meta: { modelName: 'HBSHotel' }
}
10 Replies
Hi @Matteo Giardino
The P6000 error is a generic error that is used to catch all other errors as documented here.
Can you please provide your GitHub handle so i can investigate further?
Errors | Prisma Documentation
Prisma Client, Migrate, Introspection error message reference
GitHub
gatteo - Overview
Software Developer. Problem solver. 25. gatteo has 11 repositories available. Follow their code on GitHub.
Thanks for sharing the handle, I can see that you have no accelerate usage or pulse usage so far. Can you please let us know when you encounter this error? If possible the steps to reproduce.
Correct, I never linked such github account to my prisma profile
I can give you the email of the account I currently have the issues on
I would recommend you to email us on [email protected] so that you can get dedicated support. We can continue conversation here as well if you prefer.
I prefer to continue here, here is my account email [email protected]
Thanks for sharing, I'll check the logs
The P6000 errors are due to your current plan's limit of a single query engine instance with 10 database connections, which can’t handle your request volume. We've deployed changes to help mitigate the issue, but we recommend upgrading to the Pro or Business plan to increase your connection capacity and reliably handle the load.
Thanks Raphael!
You're welcome 🙏
Hey @Matteo Giardino
We noticed that your production workspace had a surge in traffic since yesterday. This was causing Query Engine to repeatedly crash and restart and majority of queries were failing. Can you let us know if the traffic surge was expected? We tried reaching out to you via registered email.
At the moment, traffic seems to be under control. However, we wish to check if the sudden traffic was expected, so that we can take appropriate measures.