TGEgg Member invites guide 中文

Your member invite task is set to 100 people per round —
so why does each round only add a few?

Many users run into this: the task is clearly running normally, yet it seems to "add only 1 person per round (say, every 10 minutes)". This isn't a software bug — your Telegram account has been temporarily restricted by Telegram itself. Below, a real example walks through what happened, why, and what to do about it.

1What you expect vs. what actually happens

What you expected
100 people per round
One round every 10 minutes, 1,000 people done in no time
What actually happened
Only 0–3 people per round
11 rounds run, 10 people added, 980 still in the queue

Here is this task's real execution log. The light bars are the 100 people planned per round; the dark bars are how many were actually added:

Results per round (100 people planned per round)
From round 2 to round 11, Telegram stopped every round right at the start
Round 234567891011
100 people planned 0–3 people actually added
10
Invited successfully in total
10
Rejected by Telegram
980
Still waiting in the queue

2What is Telegram rejecting?

Every time a round was stopped, Telegram returned the same error: PeerFloodError. In plain English: "This account has been interacting with strangers too often lately and is temporarily restricted. For now it can basically only interact with people who have added each other as contacts (mutual contacts)."

An analogy

Think of your Telegram account as a SIM card. If that SIM makes sales calls to hundreds of strangers every day, the carrier soon flags it as a "spam number". From then on, calls to strangers never even ring — they're cut off immediately. Calls to old friends in your contacts still work fine.

Telegram applies the same logic to member invites: adding lots of strangers to groups in a short time is treated as spam. Once the account is flagged, Telegram rejects the request outright no matter how the software retries. The restriction usually lasts from a few hours to a few days, and the harder you push, the longer it lasts.

3Why does each round "stop after one or two"?

This is the system protecting your account. Here's what actually happens in each round:

1
A new round starts and invites people one by one as planned
The system invites the first person at the pace you set (30–60 seconds between people).
2
The first 1–3 people may succeed
The restriction doesn't block 100% of requests; one or two occasionally "slip through", which is why you see the odd success.
✕
Telegram refuses, and the system hits the brakes immediately
As soon as a PeerFloodError comes back, the system stops the round and returns the remaining 90-plus people to the queue untouched. Pushing on would only make Telegram tighten the restriction, or even ban the account.
3
It tries again in the next round
Ten minutes later the next round starts and the same thing happens. That's the "one person every 10 minutes" you're seeing.
Bottom line: the task isn't broken and the queue isn't lost. The real bottleneck is that this Telegram account is under Telegram's anti-spam restrictions. Raising the per-round count or shortening the intervals won't help at this point — it will make things worse.

4What to do instead

1

Pause first and let the account "cool down"Most important

Pause every member invite and DM task on this account and let it rest for at least 24 hours. The PeerFlood restriction lifts on its own, but repeatedly hitting it keeps extending it.

2

Check the restriction status with SpamBot

Use the account status check on the "TG accounts" page in TGEgg, or have the account send /start to Telegram's official bot @SpamBot. It will tell you whether the account is restricted and when the restriction ends.

3

Slow down once it recovers

We recommend 10–20 people per round, a few hours between rounds, and at least 60 seconds between people. Newly registered accounts in particular can't handle 100 people per round — better slow than banned.

4

Use sturdier accounts

Accounts that are older, have real chat history and have Telegram Premium get noticeably higher anti-spam thresholds. For important tasks, spread the work across several accounts instead of loading 1,000 people onto one.

5FAQ

I've lowered the per-round count and lengthened the intervals. Will it recover right away?

No. The restriction is recorded on Telegram's servers, and changing settings only affects future behavior. You have to wait for the restriction to lift on its own (usually a few hours to a few days). Slowing down is so you don't trigger it again afterwards.

Why do one or two invites still succeed now and then?

If the person being invited is a mutual contact of your account, or has fairly relaxed privacy settings, the invite may still go through. That's why results during a restriction don't drop to zero but trickle in.

Will the 980 people in the queue be lost?

No. Targets that haven't been processed stay in the task queue and continue automatically once the account recovers. You can also pause the task and switch to another account to handle the remaining targets.

How do I avoid getting restricted again?

Three principles: go slow (at least 60 seconds between people), keep volume low (we recommend no more than 30–50 people per account per day), and use strong accounts (older, with real usage history, ideally with Premium). Member invites are inherently high-risk; steady output always gets you to your goal faster than trying to add everyone at once.