Share feedback, ideas and get community help

Updated 11 months ago

Prisma issues

Hi guys. We are facing an error that is preventing access to the typebot builder. It seems to be a reference to a non-existent column by Prisma. Can anyone explain what might have caused this error and how to fix it? Here is the error log for reference:

2024-02-08T23:03:53.647057032Z ' at async getUserByEmail (/app/apps/builder/.next/server/chunks/524.js:1:1317)',
2024-02-08T23:03:53.647060819Z name: 'PrismaClientKnownRequestError'
2024-02-08T23:03:53.647064596Z }
2024-02-08T23:03:53.647232490Z PrismaClientKnownRequestError:
2024-02-08T23:03:53.647239874Z Invalid prisma.user.findUnique() invocation:
2024-02-08T23:03:53.647243981Z
2024-02-08T23:03:53.647247618Z
2024-02-08T23:03:53.647251495Z The column User.referral does not exist in the current database.
2024-02-08T23:03:53.647255253Z at si.handleRequestError (/app/node_modules/.pnpm/@prisma+client@5.8.0_prisma@5.8.0/node_modules/@prisma/client/runtime/library.js:125:6817)
2024-02-08T23:03:53.647259160Z at si.handleAndLogRequestError (/app/node_modules/.pnpm/@prisma+client@5.8.0_prisma@5.8.0/node_modules/@prisma/client/runtime/library.js:125:6151)
2024-02-08T23:03:53.647263047Z at si.request (/app/node_modules/.pnpm/@prisma+client@5.8.0_prisma@5.8.0/node_modules/@prisma/client/runtime/library.js:125:5859)
2024-02-08T23:03:53.647266874Z at async l (/app/node_modules/.pnpm/@prisma+client@5.8.0_prisma@5.8.0/node_modules/@prisma/client/runtime/library.js:130:9805)
2024-02-08T23:03:53.647270962Z at async getUserByEmail (/app/apps/builder/.next/server/chunks/524.js:1:1317) {
2024-02-08T23:03:53.647285900Z name: 'GetUserByEmailError',
2024-02-08T23:03:53.647290058Z code: 'P2022'
2024-02-08T23:03:53.647295248Z

Thank you in advance.
B
2 comments
It means the migration maybe did not succeed when you upgraded your instance.
Can you retrieve earlier logs? Right after you restarted the docker-compose stack?
Add a reply
Sign up and join the conversation on Discord