Bot randomly going offline with no errors..

I have exactly the same issue like this person. I didnt change anything and suddenly it has this behavior. I dont get any errors at all, and the process is still running but not doing anything.'' (Note, I have other bots running aswell and they dont have this behavior.) Is there a way to get info on what happens or possibly a fix for that?
No description
7 Replies
d.js toolkit
d.js toolkit6mo ago
- What's your exact discord.js npm list discord.js and node node -v version? - Not a discord.js issue? Check out #other-js-ts. - Consider reading #how-to-get-help to improve your question! - Explain what exactly your issue is. - Post the full error stack trace, not just the top part! - Show your code! - Issue solved? Press the button! - Marked as resolved by OP
Question
Question6mo ago
Do you have commands, button that do something other than sending an message? if yes do you have error handling? or try{}, catch{} to your codes? the reason I'm saying this is because its sometimes caused by commands :mmLol:
Flo
FloOP5mo ago
I didnt change anything as I said, it worked since yesterday till now. It didnt log anything.
[25.06.2025 - 21:52 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 100ms.
[25.06.2025 - 21:53 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 125ms.
[25.06.2025 - 21:54 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 101ms.
[25.06.2025 - 21:54 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 108ms.
[25.06.2025 - 21:55 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 102ms.
[25.06.2025 - 21:56 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 102ms.
[25.06.2025 - 21:56 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 114ms.
[25.06.2025 - 21:57 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 100ms.
[25.06.2025 - 21:58 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 105ms.
[25.06.2025 - 21:59 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 106ms.
[25.06.2025 - 21:59 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 108ms.
[25.06.2025 - 22:00 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 105ms.
[25.06.2025 - 21:52 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 100ms.
[25.06.2025 - 21:53 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 125ms.
[25.06.2025 - 21:54 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 101ms.
[25.06.2025 - 21:54 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 108ms.
[25.06.2025 - 21:55 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 102ms.
[25.06.2025 - 21:56 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 102ms.
[25.06.2025 - 21:56 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 114ms.
[25.06.2025 - 21:57 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 100ms.
[25.06.2025 - 21:58 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 105ms.
[25.06.2025 - 21:59 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 106ms.
[25.06.2025 - 21:59 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 108ms.
[25.06.2025 - 22:00 Uhr] DEBUG: [WS => Shard 0] Heartbeat acknowledged, latency of 105ms.
22:00 Uhr is the last time it was online, after that no logs anymore and yes, I have slashs, buttons and usercontext.. but everywhere is a try catch
Amgelo
Amgelo5mo ago
given it's that accurate (22 o clock), maybe there's some kind of cron running?
Flo
FloOP5mo ago
Nothing, nothing that would freeze the process. Its not every time 22;00 its random, a few days ago it was quickly after startup. Now it worked for 1 day and happened again. Still no errors whatsoever
Sutoreitso
Sutoreitso5mo ago
maybe ur host?
Sambeano
Sambeano5mo ago
I know mine timesout after a while on my windows terminal...could it be that?

Did you find this page helpful?