Telegram message not sending: what each error means, and how to fix it without breaking the rules

Telegram message not sending? A clock icon means it is still trying to send, most often because of your connection; a red exclamation mark means it failed. Beyond that, the cause is a Telegram outage, a limit on your account, the chat’s rules or the recipient’s settings. Try another chat first, then check the error Telegram gives.

Telegram message not sending: find the cause in five steps

Work from the widest cause to the narrowest. Each step rules out a whole group of problems, so you don’t waste time changing chat settings during an outage, or waiting out an outage that is really a ban in one group.

1. 1

   Look at the icon next to the message

   A clock means the app is still sending it, and an exclamation mark means it could not be sent. Telegram’s FAQ explains that one check means the message reached the Telegram cloud, and two checks mean it was read. So a message with a check was sent; if nobody replies, that’s a different problem.

2. 2

   Send something to another chat

   Try Saved Messages or a friend. If that fails too, the problem is your connection, an outage or your account. If only one chat fails, it’s that chat’s permissions or the recipient’s settings.

3. 3

   Check whether others see the same

   Outage trackers such as Downdetector collect reports from users. A sudden spike from many countries at once points to Telegram, not to you.

4. 4

   Read the error code

   Telegram’s apps often show a plain message, but the API returns a code such as CHAT_WRITE_FORBIDDEN. Tools built on the API, schedulers included, can show it. The tables below map each common code to its cause.

5. 5

   Fix the cause, then retry once

   A permission error will fail the same way every time until someone changes the setting. Retrying in a loop just repeats the same failure.

Why is my Telegram message stuck on the clock icon?

The clock means the app hasn’t yet handed the message to Telegram’s servers. Telegram’s design guidelines for its apps describe a clock while a message is being sent, and an exclamation mark next to a message the app couldn’t send. When every chat shows the clock, the cause is almost always the link between your device and Telegram, not the chat. Work through these in order:

• Switch between Wi-Fi and mobile data, or move somewhere with a better signal.
• Turn off any proxy you added in Telegram’s settings, and any VPN on the device, then try again. A proxy or VPN that has stopped working can leave every message waiting.
• Check that a data saver or battery saver isn’t stopping Telegram from using the network.
• Close and reopen the app, then update it. Older versions also miss newer features, such as paid messages (see below).
• Send from another device signed in to the same account, such as Telegram Desktop or Telegram Web. If that works, the problem is the first device.

If the clock turns into a red exclamation mark, tap it to send again (Telegram’s bug tracker describes the same button). If it fails in every chat and on every device, check for an outage next.

Is Telegram down, or is it just your account?

Two recent disruptions show what an outage looks like. On 12 March 2026, users from Europe and the post-Soviet states to Asia and North America reported that messages and media would not load, and some said messages would not send (abit.ee, dev.ua). On 8 September 2026, nearly 4,000 users in Singapore reported problems on Downdetector at the peak, with more reports from Indonesia, the Philippines, India, Malaysia, Vietnam and Thailand (The Star, The Vibes). No cause was given for either.

An outage looks like this: nothing sends in any chat, on any of your devices, and other people report the same thing at the same time. The fix is to wait, rather than sending the same message again and again.

A limited account

If only you are affected, and mainly when you write to people you don’t know, the account may be limited. Telegram’s spam FAQ says an account becomes limited when moderators confirm reports of unwanted messages. A limited account can still message people who have its number saved as a contact, and reply to anyone who writes first. A first limit usually lasts a few days, and repeated offences mean longer blocks. If you think the limit is a mistake, Telegram asks you to contact @SpamBot; see what a limited account can still do.

A frozen account

A frozen account is more serious. Telegram’s API documentation says accounts can be frozen for serious violations of its Terms of Service; they become read-only, and many actions fail with FROZEN_METHOD_INVALID (420). Telegram’s FAQ adds that while frozen you can still read your chats but can’t send messages, and that you can appeal directly from the app. A frozen account is deleted after a set time unless an appeal is accepted. Our guide to a frozen Telegram account and how to appeal covers what to do.

Permission and access errors: “You can’t write in this chat”

These are the chat’s rules, set by its owner or admins. In a channel, the owner sets each admin’s rights one by one (channels FAQ); in a group, admins can restrict members from posting certain kinds of content, or from sending messages at all (FAQ). The wording below is Telegram’s own, from the error lists of messages.sendMessage and messages.sendMedia; codes are as listed for sendMessage and can differ slightly by method.

Access errors: private chats, blocks and deleted users

These mean the account can’t reach the chat or person at all. Most of them are the other side’s decision, and the right response is to respect it.

• CHANNEL_PRIVATE (406): “You haven’t joined this channel/supergroup.” Join with the account that sends, using an invite you were given.
• USER_IS_BLOCKED (403): “You were blocked by this user.” Stop writing to them; there is nothing to fix.
• YOU_BLOCKED_USER (400): “You blocked this user.” Unblock them first if you do mean to write.
• INPUT_USER_DEACTIVATED (400): “The specified user was deleted.” Remove the account from your lists.
• PEER_ID_INVALID (404): “The provided peer id is invalid.” Check the username, link or ID you used.
• PRIVACY_PREMIUM_REQUIRED (406): “You need a Telegram Premium subscription to send a message to this user.” It’s the recipient’s privacy setting.

Slow mode and flood waits

Two errors ask you to wait rather than refusing outright. SLOWMODE_WAIT_X (420) means “Slowmode is enabled in this chat: wait X seconds before sending another message to this chat.” A related one, SLOWMODE_MULTI_MSGS_DISABLED (400), means slow mode also stops you forwarding several messages to that group at once (messages.forwardMessages).

FLOOD_WAIT_X (420) is Telegram’s rate limit. Its error reference says it means the maximum number of attempts to call a method with the same input has been exceeded, and “A wait of X seconds is required”. Unlike slow mode, it isn’t tied to one chat’s setting. Telegram doesn’t publish the thresholds. Wait the full time before you send again, and spread sends out afterwards. Our guide to Telegram flood waits goes into the number in the error and how to pace an account.

Why can’t I forward messages from this channel?

Because its owner turned forwarding off. Group and channel owners can restrict saving content, which blocks forwarding, screenshots and saving media, and since 1 March 2026 Premium users can disable sharing in a one-to-one chat. A forward from such a chat fails with CHAT_FORWARDS_RESTRICTED: “You can’t forward messages from a protected chat.” The guide to why some Telegram channels can’t be forwarded covers the related errors and what to do instead.

Paid messages: ALLOW_PAYMENT_REQUIRED

Since March 2025, Telegram Premium users can set a fee in Telegram Stars for incoming messages from people outside their contacts, and group owners can charge for messages in their groups. Premium users set it under Settings, Privacy and Security, Messages; group owners turn on “Charge Stars for Messages” under Permissions.

When a recipient charges and the send doesn’t include enough Stars, Telegram returns ALLOW_PAYMENT_REQUIRED_X (403): “This peer charges X Telegram Stars per message, but the allow_paid_stars was not set or its value is smaller than X.” The older ALLOW_PAYMENT_REQUIRED (406) is returned only to app versions without paid-message support, so update the app. According to the paid messages documentation, contacts, people the recipient has messaged first and people they have exempted don’t pay; in supergroups, admins can be exempt.

The fee is a spam filter by design. Pay it for a message the person will want, or don’t send it; never try to reach many strangers this way.

Scheduled messages that fail, and signed-out sessions

Scheduling errors

Every private chat, group, supergroup and channel has its own queue of scheduled messages (scheduled messages). Two errors come from that queue:

• SCHEDULE_TOO_MUCH (400): “There are too many scheduled messages.” Send or delete some of that chat’s queued messages first.
• SCHEDULE_DATE_TOO_LATE (400): “You can’t schedule a message this far in the future.” Pick an earlier date.

Telegram’s API documentation doesn’t publish either number, so treat a failure as the limit and plan around it. Two more details from the same page: a message scheduled less than 10 seconds ahead is sent at once, and repeating scheduled messages are a Premium feature, daily, weekly or at a few longer intervals. The guide to Telegram’s scheduled message limits has the community figures and how albums count.

Session errors

A 401 error means the session itself no longer works. AUTH_KEY_UNREGISTERED (“The key is not registered in the system”) and SESSION_REVOKED (“The authorization has been invalidated, because of the user terminating all sessions”) both need a fresh sign-in, for example after you end all other sessions from your phone. USER_DEACTIVATED means the account itself has been deleted or deactivated (error reference). If you didn’t end those sessions yourself, check who else is signed in to your account.

How do I track which Telegram messages failed?

If you post to many groups and channels, one-off troubleshooting stops scaling. Keep a record of each failure so patterns show up:

• the account that sent it, and the chat it was going to
• the time, so you can match it with an outage report
• the exact error code, not just “failed”
• what you changed, and whether the retry worked

Read the log by code. One code across many chats points to the account, such as a limit or an expired session. Different codes in one chat point to that chat’s rules. Network errors are worth retrying; permission, block and protection errors are not, until someone changes a setting.

In Dripl, failed sends and forwards appear on the Errors page with Telegram’s error, where you can retry or resolve them one at a time or in bulk. The Errors page groups failures by Telegram’s error code and shows a suggested fix for the codes it knows, such as CHAT_WRITE_FORBIDDEN, USER_BANNED_IN_CHANNEL, FLOOD_WAIT and AUTH_KEY_UNREGISTERED. A scheduled send that hits a network error is tried again five minutes later, up to three attempts in all. A forwarding rule whose account has to sign in again stops and tells you why, instead of failing on every post. Dripl also skips posts from sources with content protection and logs them as filtered instead of sending them.

• Analytics

  Sent, failed and pending Telegram messages, success rate and sending streak against the period before, ranked by account, template, recipient and proxy.

  Learn more

• Scheduler

  Send one-off and recurring messages to Telegram contacts, groups and channels at the time and in the timezone you choose, with templates and attachments.

  Learn more

• Flood wait errors

  A Telegram flood wait tells an account or bot to pause for X seconds. Learn how it differs from slow mode and 429 errors, and how to pace sends to avoid it.

  Read the guide