Already at this stage

[rafaelromcar-parabol]

Issue - Bug

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

ACTION-PRODUCTION-G8Z

We might have started seeing this error on Oct 9th at around 00:00, right after deploying v7.50.3 to production, but it's hard to tell as we keep only 14 days of Datadog logs

SEND TO SENTRY Error: Already at this stage                                                                                                                                                                        
    at resolve (/home/node/parabol/dist/gqlExecutor.js:96530:53)                                                                                                                                                   
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)                                                                                                                                  
    at async Object.MutationnavigateMeetingResolver (/home/node/parabol/dist/gqlExecutor.js:126133:22)

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.

[Dschoordsch]

Sentry Issue: ACTION-PRODUCTION-G8Z

[rafaelromcar-parabol]

Happened 5.55k times in the last two weeks. Fixing this would make our logs much easier to read

[jordanh]

Added this to the backlog for investigation

[rafaelromcar-parabol]

Hey there! I managed to reproduce this error on Staging. Very easy to do! Check my Loom https://www.loom.com/share/318404fe32434ce386fec7e4b144e8db

As I say on the video, that log line was introduced by @mattkrick during the NewMeeting Phase 3 migration. It might be useful for something, but I'm not quite sure for what, and right now it's adding a lot of noise. @mattkrick do you remember why you added that? Should we keep it?

[mattkrick]

oh that's great.
yeah, we should keep the line because it tells us that the client is sending messages to the server that aren't necessary, now that we know the root cause (thank you!) we can prevent the client from sending them in the first place

[mattkrick]

fixed in #10575