How to fix a failed Discord post in Blotato, without posting it twice
Short answer: Blotato, a software subscription that schedules and publishes posts to social networks and to Discord, shows a failed Discord post (Discord is a chat platform where communities run servers split into channels) with a numbered error code. Check the channel before you retry, because one Discord error says the message may already be there. Then match the code to its fix: give the Blotato bot the right channel permissions (36001, 36002), add a forum title (36005), shorten text over 2,000 counted characters (20005), shrink files (90010) or reconnect the server (5003). Retry once.
Your Discord post failed in Blotato, and you want to fix it without posting twice to your community.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Discord failures are easier to fix than most, because Blotato shows numbered codes and the causes are mostly permissions. The danger is the retry. One Discord error says the message may already be in the channel, so a second publish can post it twice to your community. This guide gives the safe order for Discord posts sent through Blotato: check what happened, read the code, fix one thing, retry once. For the numbers behind the rules, see the Discord limits cheat sheet.
This page may contain affiliate links from which Blur Studio earns commissions.
Step 0: check what happened before you retry
Blotato says to find a post's outcome before retrying. Open Posts in Blotato and check Scheduled, Published and Failed for the same channel. Then open the channel in Discord. Blotato names the case outright: if the error says "Discord did not confirm the post. It may have been posted.", the message might already be in the channel, so check it before you publish again. One error is the opposite: "The upload to Discord was interrupted, so nothing was posted." In that case nothing reached the channel and a retry is the fix.
| Status | Meaning | Next step |
|---|---|---|
| scheduled | Waiting | Leave it |
| in-progress | Working, or no record found. It does not prove a live job | Wait, then check Published, Failed and the channel |
| published | Recorded as live, with a link to the Discord message | Open it and stop |
| failed | An error was recorded | Read the code and follow this page |
| CANCELED | Schedule removed or moved to drafts | Not a failure |
The Discord errors and fixes, from Blotato's own list
| Code and message | Meaning | Fix |
|---|---|---|
| 36000: channel no longer exists | Someone deleted it in Discord | Post to another channel. Use Remove channel in Accounts to clear it |
| 36001: the Blotato bot cannot see the channel | No permission to view it | In channel Permissions, add the Blotato bot with View Channel and Send Messages |
| 36002: the bot is not allowed to post this | A needed permission is missing | Allow Send Messages, Attach Files, Embed Links, Create Public Threads and Send Messages in Threads |
| 36003: needs text or media, or too many files | 10 images and videos at most per post, and in a thread the limit applies to each post | Add text or media, or remove files |
| 36005: a forum post needs a title | Nothing was published | Add a title, 1 to 100 characters |
| 36006: forum only accepts posts with a tag | Blotato does not set tags | Turn off "Require people to select tags when posting" in the forum settings, or use another channel |
| 36007: server moderation rules blocked the post | AutoMod (Discord's built-in filter for banned words and links) blocked the text, title or a link | Change the text or title, or ask an admin to adjust AutoMod |
| 36004: Discord rejected the post | Discord refused the message | Send support the full error and the channel |
| 90010: file larger than the server accepts | 20 MB default, 50 MB at Level 2, 100 MB at Level 3 | Use smaller files |
| 90009: could not download the media | A link did not open, errored or had no Content-Length header (a line a web server sends with a file to say how big it is) | Use a public link whose response includes Content-Length |
| 20005: text over 2,000 characters | Emoji and full-width characters count as 2. In a thread the error names the post number | Shorten the text |
| 20003: upload interrupted, nothing posted | The upload stopped early | Publish again. If it repeats, use smaller files |
| 20003: Discord is limiting how fast Blotato can post | Rate limit on the bot | Wait a few minutes |
| 20003: Discord did not confirm the post | The result is unknown | Check the channel before publishing again |
| 20003: could not authenticate with Discord | Discord rejected the bot, not your account. Reconnecting does not fix it | Publish again later. If it repeats, contact support |
| Maximum of 100 posts in 24 hours | Blotato's cap per channel, the same on every plan | Wait, or post to another channel |
| Page / subaccount not found | The channel ID is not a connected channel | Reconnect the server and check the channel |
| 5000: channel is not connected | A scheduled post fails this way if you reconnect the server and leave the channel unchecked | Reconnect and tick the channel |
| 5003: the bot is no longer in the server | Someone removed it, or the server was deleted | Reconnect the server, tick every channel to keep, select Finish |
Top causes for Discord, in the order I would check them
Blotato does not publish counts of which Discord error is most common, so this order is by effort, from cheapest check to most expensive, not by how often each happens.
- Bot permissions (36001, 36002). A settings change in the channel. This is the usual cause for a post that works as text but fails with files or threads.
- Forum rules (36005, 36006). A missing title or a required tag.
- Content rules (36003, 20005). Count the files and count characters with emoji doubled.
- File size and links (90010, 90009). Check the server's boost level and open each link in a private window.
- AutoMod (36007). Needs an admin if the rule is theirs.
- Rate limits and cap (20003, 100 a day). Wait.
- Connection (5000, 5003). Reconnect, and tick every channel.
- Unknown result (20003, did not confirm). Check the channel first.
Fix steps in order
- Write down the server, channel, time with timezone and the exact error with its code. Copy the request ID from Logs.
- Check Published and Failed in Posts, then the Discord channel. If the message is there, stop.
- Match the code in the table and change only that one thing.
- For permission errors: in Discord, open the channel settings, then Permissions, add the Blotato bot and allow what the table names. Then in Blotato choose Reconnect on the server, authorize, tick every channel you want to keep and select Finish.
- Retry once.
- Check Posts and Discord again.
Remember that reconnecting clears the server's channel selection. Blotato says scheduled posts for a channel you leave unchecked fail when they publish. Do not delete the Discord account to refresh it: deleting removes the server and its channels from Blotato and moves future scheduled posts to drafts. Our guide to posts stuck on processing or scheduled covers the same careful order for other symptoms.
Worked example (made-up numbers)
A fitness studio posts a class schedule image to #announcements at 07:00. The text posts at 07:02 but the image does not, and Blotato shows Failed with code 36002. Her checks:
- Discord shows no message in #announcements. Published is empty. Safe to retry after the fix.
- Code 36002: the bot lacks a permission. Text needs Send Messages, which it had, but the image needs Attach Files, which it lacked.
- She adds Attach Files, Embed Links, Create Public Threads and Send Messages in Threads to the Blotato bot in channel Permissions.
- She reconnects the server and ticks both #announcements and #events, her two channels. Forgetting #events would have made the next scheduled #events post fail with code 5000.
- She retries once. At 07:30 the post shows Published with the image. Posts that day to #announcements: 1, far under the cap of 100.
How to prevent it
- Give the bot all six permissions in each channel on day one, not only the two needed for text.
- Always set a title on forum posts and avoid forums that require tags.
- Keep text under 1,800 counted characters and files under the server's size limit with room to spare.
- Use public media links that return a Content-Length header.
- When you reconnect, tick every channel you use.
- Tell your server admins before you schedule, so AutoMod does not surprise you.
- Check Failed once a day for the first two weeks.
When to contact support, and what to send
Contact Blotato support when the same code returns after the fix, when the message is in neither Published nor Failed, or when the error is "Discord rejected the post" (36004), where Blotato asks for the full error and the channel. Blotato lists in-app chat and support@blotato.com. Send: server and channel name, time with timezone, exact error with code, postSubmissionId (the reference number Blotato returns when software sends a post) if you used the API, request ID from Logs, link to any Discord message, and the checks already done. Do not send API keys or sign-in codes. See support response times and how to get help.
A test plan you can run
Blur Studio has not run Blotato. On a test server during the 7 day trial, run these and record the codes you actually see.
| Test | Pass looks like | Fail looks like |
|---|---|---|
| Text post with only View Channel and Send Messages allowed | Published | Error |
| Image post with Attach Files denied | Code 36002 | Published |
| Forum post with no title | Code 36005 | Published |
| Reconnect with one channel unticked, then a scheduled post to it | Code 5000 | Published |
| Link that does not open | Code 90009 | Published empty |
| Date | Test | Exact error text and code | Status in Posts | Request ID | Fix that worked |
|---|---|---|---|---|---|
Who should skip this route
If you post in one channel now and then, posting by hand avoids every failure above. If your forum requires tags, or you need to post into existing threads, Blotato cannot do it. Blotato fits teams that already schedule other posts and want the same update in a community channel. Its plans are listed on the Blotato website: Starter is $29 a month, billed monthly, as of November 2026. Check Blotato's pricing page for the current figure.
How this page was checked
The codes and fixes come from Blotato's Discord errors page, its publishing status guide, its Discord connect page, its error reference and its pricing page. Last checked 21 November 2026, refreshed every 90 days. Blur Studio has not run Blotato itself, so use the 7 day trial or an equivalent to confirm the exact wording you will see.
How I'd approach this
Look, read the code, fix one thing, retry once. First week: day 1, connect a test server and give the bot all six permissions. Day 2, run the five tests and save the codes in your log. Days 3 to 5, send one real update and check it landed once. Day 6, add a second channel only if the first worked. Day 7, decide whether Discord belongs in your setup. The free AI tools at /free can trim long announcements, and the free AI brainstorm call is at /ai-strategy.
Questions people ask
Why did my Discord post fail in Blotato?
Read the error code. The common ones are 36001 or 36002 (the Blotato bot lacks permissions), 36005 (forum post without a title), 36003 (no content or too many files), 20005 (text over 2,000 counted characters), 90010 (file too large for the server) and 5003 (the bot was removed).
What permissions does the Blotato bot need in Discord?
View Channel and Send Messages for text. For files and threads it also needs Attach Files, Embed Links, Create Public Threads and Send Messages in Threads. Add the bot under the channel's Permissions, then reconnect the server in Blotato.
What does Discord did not confirm the post mean?
Blotato says Discord did not confirm the result, so the message might already be in the channel. Check the channel before you publish again so it does not appear twice.
Why does my forum post fail in Blotato?
Each post to a forum channel needs a title of 1 to 100 characters (code 36005). Forum channels that require tags do not accept Blotato posts (code 36006), because Blotato does not set tags.
Why is my Discord file rejected as too large?
Code 90010 means the file is over the server's limit: 20 MB by default, 50 MB at Server Boost Level 2 and 100 MB at Level 3, per Blotato. Compress the file or use fewer, smaller files. See the Discord limits cheat sheet.
What if reconnecting does not fix a Discord authentication error?
Blotato says the error "could not authenticate with Discord" means Discord rejected the Blotato bot, not your post or account, and reconnecting does not fix it. Publish again later and contact support if it repeats.
Will my scheduled posts survive a reconnect?
Only for the channels you tick. Blotato says reconnecting clears the server's channel selection and scheduled posts for a channel you leave unchecked fail when they publish. Tick every channel you use.
More in this topic: Social media: posting limits and fixes by platform (40 guides) →