You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*Please describe the problem you are having in as much detail as possible:
After running a bot for ~ 5 hours or more, the send function likes to start "failing". It fails on this particular handle, not in any other handler.
Include a reproducible code sample here, if possible:
I don't know if its reproducible, this one send is the only one that fails with a ~ 70% success rate.
All other sends are fine.
// basic versionconststudentMessage=({tag, content, url})=>({content: `**Student :** \`${tag}\` **Message :** ${content}`,files: [url]});constresult=awaitPromise.allSettled([// fails after the bot ran for ~ 5 hours or more, doesn't fail before thatqTicket.coach.send(studentMessage(qTicket)),]);
Further details:
discord.js version: "discord.js": "^12.2.0",
Node.js version: v14.9.0
Operating system: Linux x64 5.4.57-1-MANJARO and Ubuntu 20.04.1 LTS, 5.4.0-47-generic
Priority this issue should have – please be realistic and elaborate if possible:
Normal priority ? I can imagine that this is a pretty annoying thing that users might run into - It is "solved" by restarting the bot every couple of hours, but that isn't really a viable option, even if the bot is stateless. I would rather not have to do that :D
Relevant client options:
partials: none
gateway intents: none
other: none
I have also tested the issue on latest master, commit hash:
The text was updated successfully, but these errors were encountered:
*Please describe the problem you are having in as much detail as possible:
After running a bot for ~ 5 hours or more, the send function likes to start "failing". It fails on this particular handle, not in any other handler.
Include a reproducible code sample here, if possible:
I don't know if its reproducible, this one send is the only one that fails with a ~ 70% success rate.
All other sends are fine.
Further details:
Normal priority ? I can imagine that this is a pretty annoying thing that users might run into - It is "solved" by restarting the bot every couple of hours, but that isn't really a viable option, even if the bot is stateless. I would rather not have to do that :D
Relevant client options:
The text was updated successfully, but these errors were encountered: