Fig. D07 · Docs › Automation › Anti-ban guardrails: pacing and flood-wait
two timelines, one account
Pacing: human-like delays and campaign stagger
send 3–8 s · reply 2–6 s · forward 4–10 s · join 5–15 s
0
60
120
180
240
300 s
52 s
81 s
31 s
82 s
shaded: delay before the send, ×2.5 until active
gap between targets: random 15–90 s
Flood-wait: Telegram says wait 420 s
gate: active 421–425 s · warming 1080–1140 s
sending, 30/hr
FLOOD_WAIT 420 s
other tasks held
failed task re-queued, not dropped
gate 421–425 s · status unchanged
tasks resume at normal pacing
global ceiling
10 sends per second across all accounts combined
health penalty
−15 per flood-wait in the last 7 days, capped at −45
auto-reply cooldown
60 s per chat, 12 s for AI rules; new messages fold into the pending reply