I’m having trouble with my Discord bot written in JavaScript. Everything was working fine until I made a small change to a console.log() statement. After that modification, the bot completely stopped starting up.
I tried reverting back to the previous version and it worked again. However, when I redeployed the working version to a fresh application instance, the same startup issue returned.
Here’s what I’m seeing in the logs:
2018-10-03T06:07:34.458763+00:00 heroku[worker.1]: Starting process with command `node app.js`
2018-10-03T06:07:35.019124+00:00 heroku[worker.1]: State changed from starting to up
2018-10-03T06:10:03.251656+00:00 heroku[worker.1]: Restarting
2018-10-03T06:10:03.252202+00:00 heroku[worker.1]: State changed from up to starting
2018-10-03T06:10:04.104471+00:00 heroku[worker.1]: Stopping all processes with SIGTERM
2018-10-04T06:10:04.239401+00:00 heroku[worker.1]: Process exited with status 143
2018-10-03T06:10:06.227488+00:00 heroku[worker.1]: Starting process with command `node app.js`
2018-10-03T06:10:06.907547+00:00 heroku[worker.1]: State changed from starting to up
The process seems to start successfully but then gets stuck and doesn’t proceed further. Any ideas what might be causing this?
check if your bot’s actually connecting to discord. heroku restarts processes when they don’t respond - your bot might be hanging during startup. add a simple console.log right after client.login() to see if it gets that far.
I encountered a similar issue with Discord bots on Heroku. It seems like there could be a synchronous operation blocking the main thread during startup. The change to your console.log statement may appear minor, but it could indicate a deeper issue.
Start by verifying that your bot token is still valid, ensuring it wasn’t regenerated. Additionally, ensure that all your environment variables are correctly set up in the new application instance. It’s common for bots to appear as if they’re starting while actually failing to connect to Discord’s API.
Consider adding more detailed logging around your Discord client setup and login process. If it works locally but struggles on fresh deployments, the source of the problem is likely related to your environment rather than your code.
Your worker process keeps restarting after a few minutes - Heroku’s probably killing it due to inactivity or resource issues. I’ve had this exact problem when blocking code stopped my bot from initializing properly. Since reverting that console.log fixed it temporarily, there’s likely a syntax error or the logging statement itself is hanging the app. Check your console.log syntax carefully - make sure you’re not logging undefined variables or circular references. Also look for any await statements without proper async declarations nearby. The fact that fresh deployments fail but it works locally screams environment-specific issue, not just broken code.