Error on threads/channels with Discord's Poll, Discord client restart required to temporary fix it

[Acters]

On a specific discord channel that I keep track of and there is an error that prevents Discord History Tracker from working. Only that specific channel. its really odd to only occur to one channel.

The only new thing I could see is that someone started a poll recently. Which I don't believe to be causing the issue, but I am unsure what could be causing the problem.

Restarting the website or Discord App temporarily fixes the issue, but it returns occasionally. Please advise on how to debug this further.

[chylex]

You can find the failing request in the Network tab, and copy the message data:

Could you send it to me privately, for ex. email it to [email protected]? You can redact the text contents of the messages, as the issue appears to be in emoji reactions to messages.

[Acters]

i was having this issue all morning but the second I posted this issue the problem went away. I personally think it was discord itself and not the DHT application. Likely discord distributed a quick fix in the server hosted Javascript file.
if I get the error again, then I will reopen, make sure not to reload the client, and paste the payload.

Thank you for your quick response, and sorry for bothering.

[Acters]

You can find the failing request in the Network tab, and copy the message data:

Could you send it to me privately, for ex. email it to [email protected]? You can redact the text contents of the messages, as the issue appears to be in emoji reactions to messages.

Hi chylex, I sent you the email as this issue resurfaced. As we both know there is a quick fix by reloading the client/browser. I rather make sure this doesn't occur again.

the password to the email is "$v.J]6qNT+sn,= and set to expire in about 2 weeks. Sent from Protonmail.

EDIT:
and without reloading the app, the problem went away magically, so weird, can't tell if I should just close it and forget about or to explore this further...
EDIT 2:
reappeared and seems to be consistent for now, let me know if you need more data from this weird bug.

[chylex]

I see a problem, currently not sure why it's happening. One of the messages has two reactions, except their count is 0.

Can you find a message in that channel, which was sent at June 14, 2:45:23 PM UTC? It should be between two messages that start with "and now..." and "Discord asking..."

According to the data, this message has no text, no attachments, no embeds, but has two broken reactions. If you find a message from that time and it looks like a normal message, then I wonder if it's some kind of temporary blip on Discord's side, and more investigation will be needed.

[Acters]

I see a problem, currently not sure why it's happening. One of the messages has two reactions, except their count is 0.

Can you find a message in that channel, which was sent at June 14, 2:45:23 PM UTC? It should be between two messages that start with "and now..." and "Discord asking..."

According to the data, this message has no text, no attachments, no embeds, but has two broken reactions. If you find a message from that time and it looks like a normal message, then I wonder if it's some kind of temporary blip on Discord's side, and more investigation will be needed.

That message is strictly only a poll without text, so it did not pick up the text inside the poll.
Which makes sense why it did not cause an error until there was a new poll created.
I, also, remember that when I made this issue on you github, there was a Poll created. odd
the poll had 2 votes when I sent you the request payload.
The reaction ID number corresponds to the poll option counting from the top at 1 up to the number of poll options, in this case 6 vote IDs.
There are currently 4 votes, but because there are 2 votes for the same ID number that did not duplicate the reaction ids. I would imagine it would have increased the amount but not sure. they are currently at count 0.

here is an image of the payload request of the same message, but this one was successful and did not return an error.(by reloading the website/app it temporarily "fixes" it)
Note: I redacted a lot of possibly identifiable info, but on the left side the second track messages request(which is selected, and should be causing an ERROR) did not error and was successful.
what a weird edge case, I dont understand what caused this to start causing to error.

If I make a vote on an empty option, it did not error but added the "name" param, but doesn't add the "name" param if I vote on a previously voted option by another user. weird.