Bug description
Getting the following error:
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: Internal Server Error"}} (Request ID: 9614bae48ee41975)
This is likely related to #27700 and the Prisma Postgres downtime, but I wanted to ensure it is tracked, so I filed this issue.
Is there a way to configure a fallback URL by the way? My team is currently evaluating Prisma Accelerate, and errors like this make us hesitant to roll it into production without safety nets.
Severity
🚨 Critical: Data loss, app crash, security issue
Expected vs. Actual Behavior
Expected: Prisma Accelerate requests are not failing.
Frequency
Consistently reproducible
Does this occur in development or production?
Both development and production
Is this a regression?
Yes, it was working yesterday.
Workaround
No workaround.
Bug description
Getting the following error:
This is likely related to #27700 and the Prisma Postgres downtime, but I wanted to ensure it is tracked, so I filed this issue.
Is there a way to configure a fallback URL by the way? My team is currently evaluating Prisma Accelerate, and errors like this make us hesitant to roll it into production without safety nets.
Severity
🚨 Critical: Data loss, app crash, security issue
Expected vs. Actual Behavior
Expected: Prisma Accelerate requests are not failing.
Frequency
Consistently reproducible
Does this occur in development or production?
Both development and production
Is this a regression?
Yes, it was working yesterday.
Workaround
No workaround.