Accelerate was not able to connect to your database, The underlying error is: error code: 1016
Hello there!
I just subscribed to accelerate PRO and switched my production critical time clock system for a customer (around 200 users, 30k queries per day). It seemed to works good so far for most requests except the fact that sometimes I receive an error such as:
This request could not be understood by the server: {"type":"UnknownJsonError","body":{"code":"P6008","message":"Accelerate was not able to connect to your database. The underlying error is: error code: 1016"}} (The request id was: 939892cceb9122de)
Or sometimes:
This request could not be understood by the server: {"type":"UnknownJsonError","body":{"code":"P6008","message":"Accelerate was not able to connect to your database. The underlying error is: Health Check of Query Engine timed out."}} (The request id was: 9397275c8f4cebe3)
I do not understand why this happens nor to I seem to have enough visibility on the dashboard to understand why such things happen.
This happens on prisma 5.6.0. I am looking to update to 5.22.0 soon, but I am unsure if this is related to accelerate.
Before using accelerate, I never had my supabase database being unreachable so I am unsure as to why this happens.
I looked at https://www.prisma-status.com/ and I saw no outage going on.
Any help welcomed as this is affecting my user base at the moment and its quite urgent
Thank you!
Prisma Data Platform Status
Welcome to Prisma Data Platform's home for real-time and historical data on system performance.
3 Replies
You decided to hold for human wisdom. We'll chime in soon! Meanwhile,
#ask-ai is there if you need a quick second opinion.Hi!
I am 99% sure you are Steven with whom I am talking to via email, and this is the DNS related issue from Cloudflare 🙂
Hi Nurul yes it's me. We can continue our follow up by email and after our resolutions we can always report back later here to help others in the community 🙂