← All guides · updated
Why a post was not published: 12 causes and how to check each one
Post did not go out? 12 causes: bot rights, chat_id, media limits, API errors. A symptom table and a step-by-step diagnostic order.
The most common causes are: the bot is not a channel admin, the chat_id is wrong, media exceed platform limits, or the API returns a permission error. Check the error message on the post card first — it names the cause in plain language.
A post can stay a draft, vanish from the queue or get the “error” status for a dozen reasons. Below is a check order that eliminates most of them in two minutes, and symptom notes for Telegram, VKontakte and MAX.
Quick diagnosis: five questions in two minutes
| Question | Where to look | What to do |
|---|---|---|
| Does the channel still exist? | The channel list in the service, and the platform itself | Reconnect the channel if it was renamed or deleted |
| Is the bot still an administrator? | Channel settings → administrators | Grant the “Publish messages” right again |
| Does the channel ID match? | The channel card in the service | Update the chat_id or the channel link |
| Does the token still work? | Channel card → connection status | Reissue the token and save it |
| Does the media fit the limits? | The post card and the error history | Remove the extra files or change the format |
If all five answers are “yes”, go to the publication history: it shows the platform’s response code. That beats any guesswork.
Telegram: bot rights, chat_id, media limits
- The bot is not an administrator. The “Send messages” right is not enough: the bot needs administrator status with the publishing right. After a channel ownership change the bot often loses access.
- The chat_id is wrong. For a public channel
@usernameworks; for a private one, a numeric ID like-100…. At.me/…link does not always replace the ID, especially after a rename. - The media breaks the format. Telegram takes albums of up to 10 files, but Postomat sends at most 6 per publication. An oversized file or an unsupported codec also produces an error.
- Message is too long. The limit is 4096 characters without media, 1024 in a caption. UTM labels appended at publish time also grow the text.
Also check whether the post was sent to a different channel: in cross-posting, one channel’s error must not block the others. The post card shows the result per platform.
VKontakte: token rights and community settings
- The token lacks the rights. Writing to the wall needs
wall; photos needphotos. A read-only token will be refused. - Publication from a person instead of the community. The post lands on a personal page or gets stuck in community moderation. Check that the community is selected and the token has access to it.
- The community is blocked or restricted. Then the error comes from the API, not the service — check the community status in VK settings.
- The token expired. Some token types have a limited lifetime; after it runs out, publishing silently stops working. HTTP 403 or 214 usually points at token rights or the community role — the key guide is in auto-posting to VK.
MAX: what to check on first connection
- The bot is not approved yet. MAX bot moderation takes 1–3 business days.
- The bot is in the channel with the publishing right.
- The channel’s own ID is used, not the personal chat with the bot; the token is copied whole, without spaces or line breaks.
- Chat_id missing. The bot discovers the chat_id when added to the channel; Postomat picks it up automatically — how to get a chat_id in MAX has the step-by-step check.
Media and limits
| What to check | Typical error | How to fix |
|---|---|---|
| File count | More than 6 attachments in one publication | Split into two publications or remove the extras |
| File size | The platform refuses heavy video | Compress the video or publish it as a link |
| Format | An unsupported codec or container | Re-encode to MP4/H.264 |
| Caption | Text over the photo is too long | Shorten the caption or move the text to the first comment |
The safest image formats are JPEG, PNG and WebP. Check the text length per platform in the post length calculator.
What the error codes mean
- 401 / 403. The token is invalid or lacks rights. Reissue the token and check the bot’s role.
- 404. The channel or community was not found. Update the ID or the link.
- 429. Too many requests. Wait and retry; do not send the post in a loop.
- 5xx. A problem on the platform’s side. Retry later and check the service status.
The exact error text always matters more than the code: it points at what exactly is wrong — rights, ID or format.
A check order that saves time
- Open the post card and see which channel stopped publishing.
- Check the channel status in “Channels”: is it active.
- Verify the ID and the bot’s rights on the platform itself.
- Check the media: count, size, format.
- Look at the error history and the response code.
- Fix one cause and retry the publication manually, not everything at once.
When the platform is at fault, not the tool
If the response code is 5xx, the channel is active, the rights are in order and the same post publishes manually, the problem is likely temporary. Wait 10–15 minutes and retry. If the error repeats on all channels of one platform, check the status page: the platform may be under maintenance.
Sources
- Telegram Bot API: sendMessage — chat and bot rights requirements.
- Telegram Bot API: sending files — media formats and limits.
- VK API: wall.post — publication parameters and token rights.
Links verified on 26 October 2026. Platform interfaces change; if the wording differs, trust the current documentation.
Check the channel before the first publication — and queue a week of posts ahead.
Frequently asked
Why did the post stay a draft instead of publishing?
A draft means publishing was never started: no time set, no channel selected, or the post was not sent to the queue. Check the post status and that at least one active channel exists.
What does error 403 mean on VKontakte?
Most often the token lacks wall rights or the bot is not a community admin. Re-issue the token with wall and photos rights and check the role.
Will the post publish if the bot was removed from admins?
No. The platform will reject the publication. Add the bot back as an administrator with the publishing right and retry.
How do I verify the schedule before the first publication?
Schedule a test post 5–10 minutes from now to one channel. If it goes out, the schedule and rights are set up correctly.
Try it on your own channels
Free plan: one channel and ten posts a month, no card required.
This guide is also available in Russian — the whole knowledge base exists in both languages.