---
title: "Account required to wait or throttled"
locale: en
url: https://tlg.builera.app/en/docs/troubleshooting/flood-wait
verified: 2026-10-24
app_version: "2.0"
---

# Account required to wait or throttled

Understand why an account is deferred and handle it without increasing requests rejected by Telegram.


## Symptoms

A job does not run immediately, an account is throttled, or a wait-until time is shown. The reason may contain `FLOOD_WAIT`, `SLOWMODE`, `PEER_FLOOD`, or a restriction result from @SpamBot.

Do not treat all of these as machine errors. The machine may be connected normally while Telegram does not allow the next action.

## Common causes

`FLOOD_WAIT` is a wait requirement from Telegram. The app defers the relevant type of action and applies a throttled state. `SLOWMODE` is a group's message pacing rule; it does not automatically downgrade the whole account's safety state.

`PEER_FLOOD` and restricted results from @SpamBot are more serious. The account must not automatically keep retrying as it would after a connection error.

In addition to Telegram's required wait, the app has its own precautionary periods:

| Condition | Current policy |
|---|---|
| `FLOOD_WAIT` deferral | At least **2 times** the number of seconds Telegram requires. |
| Throttled | At least **24 hours**. |
| Restricted | At least **72 hours** before recovery is possible, subject to conditions. |

These periods are not guarantees about Telegram's limits. New signals may extend the wait.

## How to fix

1. Open the account in **Accounts**.
2. Read the job's hold reason and the safety state.
3. Record when resuming can next be considered.
4. Check campaigns or automation creating requests for the account.
5. Stop request sources that are no longer appropriate.
6. Wait until the mandatory period ends.
7. For restricted accounts, run an @SpamBot check when the recovery conditions require it.
8. Use the recovery action only after obtaining the required evidence.
9. Monitor the next job's result before increasing activity.

![Account list and statuses in the Demo workspace](https://tlg.builera.app/docs-media/en/accounts.webp "Read the status before trying again")

A clean @SpamBot result does not automatically reactivate the account. Recovery still requires a person's confirmation and checks on the waiting conditions. Banned accounts cannot be recovered through this normal route.

> [!IMPORTANT]
> Do not switch to Free, change proxies, move machines, or split the same requests across other accounts to retry behavior that Telegram just blocked.

Do not create a redrive just because a job is waiting. Redrive handles certain jobs that have ended; it is not a button for skipping a wait requirement.

## If it still fails

Compare the latest error time with the current wait-until time. If the deadline keeps moving out, record the new signal instead of assuming the timer is wrong.

If the wait has ended but recovery is still unavailable, save the account ID, job ID, error code, and @SpamBot check result without sensitive data. For frozen accounts, state the current resolution status on Telegram.

See [Telegram limits](https://tlg.builera.app/en/docs/safety/telegram-limits) and [safety states](https://tlg.builera.app/en/docs/concepts/safety-states). External systems can read [account details](https://tlg.builera.app/en/docs/reference/rest/accounts.get), MCP `accounts_get`, before asking you to act.