FAXES Documentation > Overflow Bot > OverflowBot Error Codes

OverflowBot Error Codes

FAXES

Since the release of OverflowBot 1.2, error codes have been introduced to help with debugging and getting precise information relating to any possible issues. Debugs and error codes are usually only shown if debug_mode is set to true in the bots config. However, error codes may be shown if the error is fatal or more serious.

Error codes are formatted in color based on some information.

  • Blue: represents informational output. This is usually not an error.

  • Yellow: means that the error or issue shown should be fixed ASAP. or a function failed.

  • Red: means something is fatal or serious and should be fixed in most cases.

Below, you can find all the registered error codes, what they mean and possible ways to resolve them.


Set One - Informational

Error Num. What does this error mean? Solution
006 The bot is pinging the associated SQL server to ensure the connection is active. If this fails the application could crash. In this case the SQL server connection timeout needs to be reconfigured.
010 The mentioned command has been ran by a user.
019 The mentioned user was banned via Id as they're not in the guild.
026 The user had their chat level removed as they left the guild (only prints if enabled).
049 The mentioned users message was auto replied to as it contains required auto-reply content.
050 This is a general informational message. The print will be different every time and only outputs non-issue related content.
006
006
006
006
006
006
006

Error Num. What does this error mean? Solution
001 The supplied bot token in the config file is not valid. Ensure the token is correct and valid in the config file compared to the Discord developer page.
002 The bots activity status could not be set. Review your config file for the game type, game and status values and make sure they're valid.
003 The bots "insufficient permissions" message could not be deleted. This is usually caused as the message is already deleted or the bot doesn't have permissions.
004 The command logging embed could not be sent. Check that the bot has permissions and that the selected channel exists.
005 Channel (CHANNEL_ID) not found for 'command_logging_channels'. Check that he channel ID in the config file is correct and the bot has permissions.
006
006