Troubleshoot Discord API and webhook errors for missing channels, missing guilds, invalid tokens, empty messages, oversized attachments, permission gaps, slowmode, and JSON validation. Use this guide to decide whether to recreate a webhook, adjust permissions, shrink content, or wait.
Last updated: May 2026
10 documented error patterns across 6 categories
Clear guidance on reconnecting, retrying, replacing media, or changing content
Official platform references plus bundle.social production troubleshooting notes
Error categories
10 documented errors
All error codes
2 mapped cases
10003Fix inputDiscord could not find the target channel.
Refresh the channel ID and confirm the bot can access the server and channel.
10004Fix inputDiscord could not find the target guild.
Reconnect Discord or verify the server connection still exists.
2 mapped cases
10015ReconnectDiscord could not find the webhook.
Create a new webhook or reconnect the Discord integration.
40001ReconnectDiscord rejected the token.
Reconnect or rotate the integration token.
2 mapped cases
20016Retry laterDiscord slowmode blocked the message.
Wait for channel slowmode to expire before retrying.
20028Retry laterThe channel write rate limit was reached.
Queue messages and retry after Discord's rate-limit window.
1 mapped case
40005Fix inputThe request body or attachment is too large.
Reduce message payload, embeds, or file size before retrying.
2 mapped cases
50006Fix inputDiscord cannot send an empty message.
Include message content, embeds, attachments, poll data, or forum starter content.
50035Fix inputDiscord rejected the request body.
Validate nested message, embed, poll, attachment, and forum fields.
1 mapped case
50013Fix inputThe bot lacks permission for the action.
Grant Send Messages, Embed Links, Attach Files, thread, or forum permissions as needed.
A Discord message can fail because the webhook was deleted, the bot lost access to the channel, the server changed permissions, the channel was archived, slowmode is active, or the message body is invalid.
Discord validation errors can come from embeds, attachments, mentions, polls, forum starter messages, empty content, or invalid nested fields. Simplify the payload before retrying.
Discord rate limits and slowmode failures should be retried only after the retry-after window. Immediate retries can create more failed sends.
If Discord cannot find the webhook or rejects the token, reconnecting or recreating the webhook is usually the correct fix. Changing the message body will not help.
bundle.social separates Discord delivery failures by webhook existence, token validity, guild and channel access, permissions, message body validation, attachment size, slowmode, and rate limits.
Retry only temporary platform failures, processing delays, timeouts, 5xx responses, and rate-limit errors after the platform allows it. Do not retry the same request when the failure is caused by expired tokens, missing permissions, unsupported media, invalid captions, duplicate content, account restrictions, or policy blocks. The same payload will usually fail again until the account, media, content, or platform-specific setting is fixed.
Platform APIs change. Use these links to confirm current error behavior and field support.
Discord errors are usually stable numeric JSON codes, but the same send attempt can fail because of channel type, bot permissions, webhook state, slowmode, or nested payload validation.
No. Reconnect or recreate Discord webhooks for missing webhook or invalid token errors. For missing permissions, empty messages, oversized payloads, slowmode, or invalid JSON fields, fix the server or message configuration first.
bundle.social keeps Discord's JSON code attached to the job and turns channel, webhook, permission, payload, and rate-limit failures into concrete next actions.
Related
Build with less platform drag