• index.js: https://gist.github.com/daggerbyte/57c12a797949b939ec800a8738860fa0
• interactionCreate.js: https://gist.github.com/daggerbyte/3c4d5c41f54b53554c0aa4bc843e594d
• poll.js: https://gist.github.com/daggerbyte/54014261c95dfba675c13850a70e4da9

I have a Discord.js /poll slash command that is set up to store voting results on a MongoDB so that, if the application goes down for whatever reason, the voting states for any outstanding polls can be retrieved once the application goes back up. Or at least, that’s the goal. Here’s the issue I’m having with it:

I can start the application/bot node . logged as…

...Beep-boop...! R1N is on-line!
Connected to MongoDB Atlas

I can create the poll in Discord.

I can vote for the poll using the buttons on the resulting embed interaction, logging as this:

Interaction collected
Interaction ID: 1246188518967873631
Poll Data: {
  _id: new ObjectId('665a298062b1781646c29dd7'),
  messageId: '1246188518967873631',
  channelId: '1245054951084920902',
  guildId: '1117541797527293952',
  prompt: 'test',
  options: [
    {
      label: '1',
      emoji: '<:a_:1245594156890587137>',
      count: 0,
      voters: []
    },
    {
      label: '2',
      emoji: '<:b_:1245594145804779530>',
      count: 0,
      voters: []
    },
    {
      label: '3',
      emoji: '<:c_:1245594134253801513>',
      count: 0,
      voters: []
    }
  ],
  type: 'letters',
  showPercentage: true,
  multiChoice: false,
  anonymous: false,
  limit: 0
}
Options after fetching: [
  {
    label: '1',
    emoji: '<:a_:1245594156890587137>',
    count: 0,
    voters: Map(0) {}
  },
  {
    label: '2',
    emoji: '<:b_:1245594145804779530>',
    count: 0,
    voters: Map(0) {}
  },
  {
    label: '3',
    emoji: '<:c_:1245594134253801513>',
    count: 0,
    voters: Map(0) {}
  }
]
Selected Option: {
  label: '1',
  emoji: '<:a_:1245594156890587137>',
  count: 0,
  voters: Map(0) {}
}
Previous Votes: []
Selected Option after vote: {
  label: '1',
  emoji: '<:a_:1245594156890587137>',
  count: 1,
  voters: Map(1) { '590630085607030784' => '<@590630085607030784>' }
}
Options after vote: [
  {
    label: '1',
    emoji: '<:a_:1245594156890587137>',
    count: 1,
    voters: Map(1) { '590630085607030784' => '<@590630085607030784>' }
  },
  {
    label: '2',
    emoji: '<:b_:1245594145804779530>',
    count: 0,
    voters: Map(0) {}
  },
  {
    label: '3',
    emoji: '<:c_:1245594134253801513>',
    count: 0,
    voters: Map(0) {}
  }
]
Poll data updated in MongoDB

I can even unvote for my votes on the poll using the same buttons that show what I voted for. There is also supporting evidence in MongoDB that the voting results are being stored there during the session in which the poll was created.

However, when the app goes down Ctrl+C, and then I bring it back up again node ., the voting/unvoting no longer works correctly. It’s difficult to recreate the pattern of behavior at this point, but, if I voted for the poll before the restart, I seem to be able to click and click and click on that vote without it performing any changes to the poll embed… just ending each time after thinking about it with “This interaction failed.” If I then click on any other unvoted button, the application stops and logs this TypeError about my index.js:

              selectedOption.voters.set(i.user.id, `<@${i.user.id}>`);
                             ^

TypeError: Cannot read properties of undefined (reading 'voters')
    at InteractionCollector.<anonymous> (C:UserssnakeOneDriveDocumentsdiscordR1Nindex.js:92:30)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

If I hadn’t voted on the embed before the restart, I seem to get up to 3 failed clicks before the app goes down for the same reason.

I’ve been down the rabbit hole on this and have also tried using ChatGPT, Code Copilot (in ChatGPT), Github Copilot, and regular Copilot. No dice. They’ve only made the issue worse. This also serves to announce you may identify some needless code because of my adventures.