umami: Argument `websiteId` is missing.

Describe the Bug

Found in the console

Database

PostgreSQL

Relevant log output

umami-1  | PrismaClientValidationError: 
umami-1  | Invalid `prisma.websiteEvent.create()` invocation:
umami-1  | 
umami-1  | {
umami-1  |   data: {
umami-1  |     id: "9051123e-d9bc-40f3-aaf5-c15a2199b833",
umami-1  |     sessionId: undefined,
umami-1  |     urlPath: "/home",
umami-1  |     urlQuery: undefined,
umami-1  |     referrerPath: "/",
umami-1  |     referrerQuery: undefined,
umami-1  |     referrerDomain: undefined,
umami-1  |     pageTitle: "------------",
umami-1  |     eventType: 1,
umami-1  |     eventName: null,
umami-1  | +   websiteId: String
umami-1  |   }
umami-1  | }
umami-1  | 
umami-1  | Argument `websiteId` is missing.
umami-1  |     at ri (/app/node_modules/@prisma/client/runtime/library.js:119:5888)
umami-1  |     at ai.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:126:6431)
umami-1  |     at ai.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:126:6109)
umami-1  |     at ai.request (/app/node_modules/@prisma/client/runtime/library.js:126:5817)
umami-1  |     at async l (/app/node_modules/@prisma/client/runtime/library.js:131:9709)
umami-1  |     at async h (/app/.next/server/pages/api/send.js:1:2849)
umami-1  |     at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16545)
umami-1  |     at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16981)
umami-1  |     at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:556:9)
umami-1  |     at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:268:37) {
umami-1  |   clientVersion: '5.9.1'
umami-1  | }

Which Umami version are you using? (if relevant)

2.10.2

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Docker

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 22 (3 by maintainers)

Most upvoted comments

Re-opening. Found the issue and will push out a fix.

Found the Same Error in the Logs of a self-hosted umami:

PrismaClientValidationError: Invalid prisma.websiteEvent.create() invocation: { data: { id: “XXXXXXXXXXXXXXXXXXXXXXX”, sessionId: undefined, visitId: “XXXXXXXXXXXXXXXXXXXXXXXX”, urlPath: “#/XXXXXXXXXXXX”, urlQuery: undefined, referrerPath: “#/”, referrerQuery: undefined, referrerDomain: “”, pageTitle: “XXXXXXXXXXXXXXX”, eventType: 1, eventName: null,

  • websiteId: String } } Argument websiteId is missing. at Tn (/app/node_modules/@prisma/client/runtime/library.js:115:5888) at In.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:122:6510)

Client Version:5.11.0

Same problem. After I reset the website data the error is gone.

Probably something related with session data since I started using that yesterday (umami.identify) and all the sites that are not using it are working fine.

Self-hosted umami-software/umami:mysql-v2.14.0.

Me too. Still encountering the sam issue. Sometimes it works well, sometimes it fails.

  • self hosted docker
  • Umami (v2.14.0)
  • Postgres
  • image: docker pull docker.umami.is/umami-software/umami:postgresql-latest

We have a deployment with data in the table, and some users are unfortunately triggering this error still. Still diving into it…

i’m seeing this problem in 2.13.2 also

2024-08-31T18:34:20.826110+00:00 analytics npx[814]: Argument `websiteId` is missing.
2024-08-31T18:34:20.826122+00:00 analytics npx[814]:     at An (/opt/umami/node_modules/@prisma/client/runtime/library.js:114:7526)
2024-08-31T18:34:20.826135+00:00 analytics npx[814]:     at _n.handleRequestError (/opt/umami/node_modules/@prisma/client/runtime/library.js:121:7392)
2024-08-31T18:34:20.826147+00:00 analytics npx[814]:     at _n.handleAndLogRequestError (/opt/umami/node_modules/@prisma/client/runtime/library.js:121:7057)
2024-08-31T18:34:20.826160+00:00 analytics npx[814]:     at _n.request (/opt/umami/node_modules/@prisma/client/runtime/library.js:121:6741)
2024-08-31T18:34:20.826173+00:00 analytics npx[814]:     at async l (/opt/umami/node_modules/@prisma/client/runtime/library.js:130:9355)
2024-08-31T18:34:20.826185+00:00 analytics npx[814]:     at async x (/opt/umami/.next/server/pages/api/send.js:1:2791)
2024-08-31T18:34:20.826197+00:00 analytics npx[814]:     at async K (/opt/umami/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
2024-08-31T18:34:20.826210+00:00 analytics npx[814]:     at async U.render (/opt/umami/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
2024-08-31T18:34:20.826223+00:00 analytics npx[814]:     at async NextNodeServer.runApi (/opt/umami/node_modules/next/dist/server/next-server.js:600:9)
2024-08-31T18:34:20.826236+00:00 analytics npx[814]:     at async NextNodeServer.handleCatchallRenderRequest (/opt/umami/node_modules/next/dist/server/next-server.js:269:37) {
2024-08-31T18:34:20.826248+00:00 analytics npx[814]:   clientVersion: '5.17.0'
2024-08-31T18:34:20.826260+00:00 analytics npx[814]: }

database: postgres version: 2.13.2 selfhosted non-docker

@mikecao could this please be re-opened?