Telegram limits
FloodWait, spam block and account bans: what they are, how to tell an account is restricted, safe volume guidelines for fresh and warmed-up accounts, and what to do if a restriction has already been received.
Telegram protects itself from spam and bots: if an account acts too often or too uniformly, Telegram restricts it. These restrictions come from Telegram — Multogram can't lift or bypass them, but you can work in a way that triggers them less often.
Kinds of restrictions
| Restriction | What it looks like | How serious |
|---|---|---|
| FloodWait — a rate limit | The log shows "Telegram rate limit — retry after a pause (RATE_LIMITED, N s)", status Flood wait | Temporary: from seconds to hours. It passes by itself |
| Spam block — a spam restriction | "Telegram restricted the account for spam" (PEER_FLOOD), status Restricted | The account can't write to strangers. Temporary — for days, or indefinite |
| Ban — a block | "The account is banned by Telegram", status Banned | The account is lost |
| Session reset | "The account's session is no longer valid", status Invalid session | You need to sign in again; often a sign that Telegram is suspicious |
FloodWait
A FloodWait means "wait N seconds": Telegram rejects the action until the waiting time has passed. The number in the log is how long to wait.
- Short (seconds to minutes) — you slightly exceeded the rate. Increase the delays in the mode.
- Long (hours) — the account is doing too many similar actions. Stop the tasks on it until the wait is over.
The application waits out a few seconds by itself and repeats the action. A longer wait is decided by the Pause account on FloodWait setting (Mailer has its own, Stop on FloodWait):
- on (the default) — the account stops working in the task, and the log line ends with the words "the account stops working in this task"; the other accounts continue;
- off — the account waits out the restriction up to 15 minutes ("waiting N s and continuing") and keeps working; a longer FloodWait stops it anyway.
Details in FloodWait: what happens to the account. If FloodWait keeps happening, increase the delays and reduce the volume.
Spam block
A spam block is a restriction on messages to people who didn't write to you first and haven't added you to their contacts. It is most often caused by mass messages, invitations and complaints from recipients.
How to check: tick the accounts and run the Check restrictions mass action — it asks the @SpamBot bot. The account's row gets the Active or Restricted status, and the message shows the end date if the restriction is temporary.
What to do: take the account off mailings and inviting until the restriction ends. The account can still read, subscribe, react and answer those who wrote first.
Safe guidelines
Telegram doesn't publish exact limits, and they depend on the account's age, its history, the number's country and the proxy. Below are cautious guidelines per account per day. Start with lower values.
| Action | Fresh account (under a week) | Warmed-up account |
|---|---|---|
| Messages to strangers | Not recommended | 10–30 |
| Comments | 3–5 | 20–50 |
| Joining channels and groups | 3–5 | 15–30 |
| Invitations to a group or channel | Not recommended | 10–30 |
| Reactions and views | 10–20 | 100 or more |
| Creating channels | 1 | 2–5 |
How to reduce the risk
Warm up new accounts. Several days of calm activity before mass work — views, subscriptions, reactions, chatting between your own accounts.
One account, one proxy. Telegram links many accounts on one IP together. Mobile and residential proxies are better than server ones.
A filled-in profile. Name, photo and bio — an account without them looks like a bot. See Profile Customizer.
Different texts. Lists of variants, spintax or AI instead of one message for everyone.
Random delays and pauses between runs. Don't reduce delays to the minimum, and don't run heavy tasks on the same accounts back to back.
A test batch. Every new scenario first on 2–3 accounts. Watch the share of errors in the log.
A consistent region. The account's number country, proxy, language and time zone should match.
Common questions
Can a spam block be lifted?
You can try through @SpamBot: the bot offers to file an appeal. Telegram makes the decision. If the restriction is temporary, it is lifted by itself on the given date.
Does Multogram protect against bans?
No tool fully protects against Telegram's restrictions. Multogram gives you delays, proxies, different texts and devices, but the outcome depends on how you use the accounts.
Why was an account restricted if I did almost nothing?
Possible reasons: a fresh or purchased account with a bad history, a "dirty" proxy, complaints from recipients, a number from a country Telegram treats more strictly. Check the account with Check restrictions and let it rest.
What should I do with banned accounts?
They can't be restored. Delete them from the database or move them to a separate table so they don't end up in tasks.
Updated
Errors and messages
What Multogram's messages mean: error screens at application start, refusals when a task starts, errors in the task log (session, chat access, privacy, FloodWait, username, invitations), AI assistant and ticket errors — what each one means and what to do.
Questions and answers
Answers to common questions about Multogram by topic: about the program, plans and billing, accounts and proxies, tasks and modes, plus questions about each automation mode.