Troubleshooting

Start by saving your changes, deploying the bot, and confirming it is running. Check the bot logs after reproducing the problem, then use the matching section below.

Intents and invite permissions

BotDen calculates the invite's permission request from enabled modules and saved command/event actions. Use BotDen's generated invite and complete Discord's authorization screen; you do not need to build a permission list yourself.

Privileged intents are separate. They control which information Discord sends to the bot and must be enabled by the bot owner in the Discord Developer Portal. An invite cannot enable them. Follow the intent setup steps for the features you use.

The bot will not start or events are missing

• If the logs report disallowed intents, open the bot's application in the Discord Developer Portal, select Bot, and enable the required options under Privileged Gateway Intents. Save and redeploy.
• For member joins, departures, or member updates, check Server Members Intent.
• For keyword replies or flows that read message text, check Message Content Intent.
• For online status or activity changes, check Presence Intent.
• Confirm the module or event handler is enabled and test a new event after deploying. Joining before the bot starts does not replay a welcome event.

Enable the intents your configured features require. If Discord indicates approval is required for an intent, complete that process for the application.

A command is missing or does not respond

Confirm the command is saved and deployed in the intended server or global scope. Discord can take time to show registration changes. Check the invoking member's command permissions and the channel's application-command restrictions.

Avoid conflicting names between a custom command and an installed module command unless you are using a supported module override. Check the module's guide for current command availability and limitations.

A feature added later reports missing permissions

Adding a module or graph action updates newly generated invite requests; it does not silently change permissions in servers where the bot already belongs. Open a fresh BotDen invite, select the existing server, and authorize the updated request. You do not need to remove the bot first.

If the error remains, inspect that server's bot role and the affected channel. A server member with the relevant management permissions may need to update them. Generating an invite alone does not change anything until it is authorized in Discord.

The bot cannot send, read, or create something in a channel

Check that the configured channel belongs to the intended server and still exists. Category and channel overrides can deny access even when the bot has the permission on its role.

Use the error in the bot logs to check the relevant permission, such as View Channel, Send Messages, Embed Links, Attach Files, Manage Channels, or thread permissions. For private ticket or moderation channels, check the bot's access to that specific channel. An invite does not rewrite your channel overrides.

Role assignment or moderation fails

Move the bot's highest role above the roles it should assign and the members it should moderate. Discord does not let the bot manage higher roles or moderate the server owner. Integration-managed roles cannot be assigned like ordinary roles.

If the logs report a missing role or moderation permission, authorize an updated invite and check the server's bot role. Separately, verify that the person invoking the command has the required command permissions.

An image, DM, RSS item, or webhook does not arrive

• Images: check the background URL and Image Cards limits. Use generated image references in the same flow. Welcome text still sends if its image cannot be generated.
• DMs: the recipient may block DMs. A Try DM action can continue the flow when delivery fails.
• RSS: the first successful check establishes a baseline and posts no old items. Wait for a new entry and the next check. See RSS Feeds.
• Webhooks: an accepted event may still be waiting for delivery. Keep the bot running and inspect its delivery status and logs. See Webhook Relay.

For all channel deliveries, check the destination and its overrides if the logs report a Discord permission error.

A graph variable is blank or a branch does not run

Check that the node is connected, the variable belongs to the selected trigger, and an earlier node loads or produces its value. Button clicks and form submissions start new interactions; reload persistent values needed by those branches. See template variables and the visual editor guide.