prisma: Calls to certain table suddenly not working in production

Bug description

I have a next.js app using the T3 stack with TRPC and Prisma, my db is hosted on planetscale.

Since yesterday calls to a specific table are suddenly not resolving. Locally everything works perfectly and every call goes through. However for my production deploy on Vercel these calls are simply not doing anything, they keep loading. I’m not getting any errors.

Everything works fine locally, my data seems to be in order through prisma studio as well. I updated all packages yesterday and just now again as I saw a new release for the Prisma client was available.

I’m at wits end…

How to reproduce

Expected behavior

No response

Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup

OS: MacOs
Database: Planetscale
Node.js version: v19.9.0

Prisma Version

prisma                  : 4.3.1
@prisma/client          : 5.4.1
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine c875e43600dfe042452e0b868f7a48b817b9640b (at ../../../../../../opt/homebrew/lib/node_modules/prisma/node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
Migration Engine        : migration-engine-cli c875e43600dfe042452e0b868f7a48b817b9640b (at ../../../../../../opt/homebrew/lib/node_modules/prisma/node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core c875e43600dfe042452e0b868f7a48b817b9640b (at ../../../../../../opt/homebrew/lib/node_modules/prisma/node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt c875e43600dfe042452e0b868f7a48b817b9640b (at ../../../../../../opt/homebrew/lib/node_modules/prisma/node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.3.0-32.c875e43600dfe042452e0b868f7a48b817b9640b
Default Engines Hash    : c875e43600dfe042452e0b868f7a48b817b9640b
Studio                  : 0.473.0

About this issue

Original URL
State: closed
Created 9 months ago
Comments: 18 (8 by maintainers)

Most upvoted comments

Good news and bad news, the issue resolved itself. I however still do not know what caused it.

NathanVG on Oct 5, 2023

I have support cases running with Planetscale and Vercel. If this gets solved I will report back here.

For posterity, this is an issue in the vercel repo from someone with the same issue: https://github.com/orgs/vercel/discussions/4368#discussioncomment-7196111

@aqrln thank you for the help!

NathanVG on Oct 5, 2023

Okay so update,

I accessed deploys from before the issues started, and I have the same issues there, only the same call not working. So I think that means I can assume it’s not a bug I introduced or a package that’s out of date, it has to be either a Vercel issue or a Planetscale issue.

NathanVG on Oct 5, 2023

Also, unrelated to your problem, but I noticed that the Prisma CLI and Prisma Client versions in your prisma -v output are diverging, and the CLI is very old. They must always be the same version and updated together.

aqrln on Oct 5, 2023

I will close this issue for now since it looks like it’s not a Prisma issue indeed. Please do let us know right away if you have any new findings that point at any potential problems in Prisma so that we reopen this issue and investigate. Also let us know if there’s anything else we can help with!

aqrln on Oct 5, 2023