Insert or update on table "Notification" violates foreign key constraint "fk_userId" at upsertTeamPromptResponse

[rafaelromcar-parabol]

Issue - Bug

• How serious is the bug? P2?
• OS: macOS / Linux / Windows / ?
• Browser: Chrome / Safari / Lynx / ? + version
• Node version: node --version
• NPM version: npm --version
• Parabol v8.11.0

error: insert or update on table "Notification" violates foreign key constraint "fk_userId"
      at /home/node/parabol/dist/node_modules/pg/lib/index.js:2749:17
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async PostgresConnection.executeQuery (/home/node/parabol/dist/gqlExecutor.js:1440351:28)
      at async /home/node/parabol/dist/gqlExecutor.js:1454834:28
      at async DefaultConnectionProvider.provideConnection (/home/node/parabol/dist/gqlExecutor.js:1440904:20)
      at async DefaultQueryExecutor.executeQuery (/home/node/parabol/dist/gqlExecutor.js:1454833:16)
      at async InsertQueryBuilder.execute (/home/node/parabol/dist/gqlExecutor.js:1450836:24)
      at async createTeamPromptMentionNotifications (/home/node/parabol/dist/gqlExecutor.js:128314:3)
      at async upsertTeamPromptResponse (/home/node/parabol/dist/gqlExecutor.js:132918:25)
      at async Object.upsertTeamPromptResponse (/home/node/parabol/dist/gqlExecutor.js:102418:14)
      at PostgresConnection.executeQuery (/home/node/parabol/dist/gqlExecutor.js:1440371:69)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /home/node/parabol/dist/gqlExecutor.js:1454834:28
      at async DefaultConnectionProvider.provideConnection (/home/node/parabol/dist/gqlExecutor.js:1440904:20)
      at async DefaultQueryExecutor.executeQuery (/home/node/parabol/dist/gqlExecutor.js:1454833:16)
      at async InsertQueryBuilder.execute (/home/node/parabol/dist/gqlExecutor.js:1450836:24)
      at async createTeamPromptMentionNotifications (/home/node/parabol/dist/gqlExecutor.js:128314:3)
      at async upsertTeamPromptResponse (/home/node/parabol/dist/gqlExecutor.js:132918:25)
      at async Object.upsertTeamPromptResponse (/home/node/parabol/dist/gqlExecutor.js:102418:14)
      at async Object.MutationupsertTeamPromptResponseResolver (/home/node/parabol/dist/gqlExecutor.js:144354:22) {
    locations: [ [Object] ],
    path: [ 'upsertTeamPromptResponse' ]
  }

Pattern and example

Acceptance Criteria (optional)

Users can:

• Do this
• Do that
• Cannot do that
  Triage is performed to find the root cause of the bug, timeboxed to ~1 hour.

Estimated effort: 1 hour to triage. More if root cause is already identified.

[mattkrick]

this happens for meetings that were created during about a 24-hour window when at-mentions in tiptap stored the teammemberId instead of the userId. I'll have to dig into who is causing this error. if it's just 1 team that keeps re-using the same meeting, i'm inclined to just let it be.