Skip to main content

Troubleshooting

Logs​

Most problems show up in your app's logs. You can find them under Logs in the sidebar, or in the Logs tab on the left side of the flow editor, which shows the last 10 logs of that command or event listener.

When a block fails, Kite logs an error with the type of the block and the reason, and the rest of the flow doesn't run. You can add your own logs with the Log Message block, for example to check the value of a placeholder. To handle errors yourself instead, put the blocks that can fail after a Handle Errors block.

Logs are kept for 30 days.

My Bot Is Offline​

Open the dashboard of your app. If the app was stopped, a popup tells you why.

  • No credits remaining: Your app used all of its credits for this month. Click on Start App in the settings once the new month has started or you have more credits.
  • Your bot token stopped working: Discord no longer accepts the token, usually because it was reset. Click on Reset Token under Bot in the Discord Developer Portal, copy the new token and click on Update token in the popup or under Credentials in the settings.
  • Your bot needs privileged intents: Some of your event listeners need intents that are turned off for your bot. Turn them on under Bot in the Discord Developer Portal, then click on Start App in the settings.
  • Failed to connect to gateway: Kite couldn't connect your bot to Discord. Click on Start App in the settings to try again.
  • Too many servers: Your app is in more servers than your plan allows. Remove your bot from some servers in Discord, or get Premium, then click on Start App.

My Command Doesn't Show Up​

Kite updates your commands in Discord a few seconds after you save them. The Commands page shows if that worked. If Discord rejected your commands, it shows why and which command caused it. Fix that command and save it again.

Disabled commands don't show up in Discord. Check that the command is enabled in the list of commands.

Your app has to be running for its commands to be updated. If it was stopped, start it and Kite updates them right away.

If it still doesn't show up, restart your Discord client with Ctrl+R, and check that your app was invited to the server with Invite app on the dashboard.

My Command Says "The application did not respond"​

Every command has to respond, usually with a Create response message block. Discord gives up after 3 seconds, so if your flow takes longer, add a Defer response block at the start. Check the logs in case a block failed before the response.

My Event Listener Doesn't Run​

  • Kite ignores messages sent by bots, including your own.
  • Message events need the Message Content Intent to see the text of messages, and member events need the Server Members Intent. Enable them in the Bot section of the Discord Developer Portal.
  • Changes to event listeners can take up to a minute to apply after saving.
  • Check that the event listener is enabled in the list of event listeners.