Error reference
Bot errors, explained and fixed.
The errors that come up again and again when you build and host a bot, what each one actually means, and what to change. Find yours below, or search this page for the text you are seeing.
Discord
4014 Disallowed intents
Your code asks for a privileged intent the Developer Portal has not switched on.
50013 Missing Permissions
The bot lacks a permission here, or its role is below the member it is acting on.
50001 Missing Access
The bot cannot see the channel or server it is trying to use.
Invalid token
The token is wrong, empty, or has been reset by Discord.
429 Rate limited
The bot is sending requests faster than Discord allows, or making too many failing ones.
10062 Unknown interaction
The bot answered a slash command too late, or another copy answered first.
50035 Invalid Form Body
Something in what the bot sent is empty, too long or the wrong type. The error names the field.
Telegram
409 Conflict
Two copies of the bot, or a leftover webhook, are fighting over one token.
403 Bot was blocked
The user blocked the bot or deleted their account. Expected; handle it rather than fix it.
429 Too Many Requests
The bot sent messages faster than Telegram allows. Wait the time it gives, then pace sends.
Node.js
Reading an error
Most of these errors carry a number, and the number is the useful part. Discord's API errors are five-digit codes like 50013; its gateway closes the connection with four-digit codes like 4014; Telegram uses HTTP statuses like 409. Search this page for the number before you read the rest of the message.
If the error scrolled past too fast to read, your hosting console keeps it. The line that matters is usually the first one that is not indented; everything under it is the stack trace showing where it happened.