I'm Not Getting Alerts

The single most useful page in the docs. Walk it top to bottom — most issues are caught in the first three checks.

Start here: check basic status

Send /tier to the bot. The reply confirms:

Whether your account is active
Your current tier and expiry date (if paid)
Your wallet count vs your tier’s limit

If /tier itself fails to respond, jump straight to D. Telegram delivery issues — the bot is alive (every other user is getting alerts as you read this), so silence on your end is a delivery problem.

If /tier does reply, follow the questions below.

Did you get any alerts at all in the last hour?

The most useful split. Pick the branch that matches.

”No alerts at all” → A. Account-level

”I get some alerts but not the ones I expected” → B. Filtering

”It worked yesterday, today nothing” → C. State change

”It works in DM but not in my group” → E. Group-specific

A. Account-level issues

Three things at the account level can stop all alerts.

A1. Your subscription expired

By far the most common cause. If you were on Pro / Elite / Exclusive and it lapsed, and you’re tracking more wallets than the free tier allows (50 EVM, 3 Solana), alerts are paused until you renew or remove wallets.

You should have already received warnings — the bot sends:

A reminder 7 days before expiry
A notification on expiry day
Follow-ups on days 1 and 2 after expiry

If you missed those, just send /tier to confirm. The reply will show your current tier and expiry. If it’s expired:

Renew with /upgrade — pick a duration, pay on-chain, tier reactivates the moment the tx confirms.
Or downgrade: open the dashboard, remove enough wallets to be under the free limit (50 EVM / 3 SOL). Alerts resume immediately for the wallets you keep.

A2. Your account was paused for inactivity

Accounts on free or early-adopter tier that haven’t interacted with the bot for an extended period get auto-paused. You’d have received one Telegram message with a ▶️ Reactivate button when this happened.

Fix: tap the reactivate button, OR just send any command (/start, /list, /help) — interacting with the bot in any way clears the paused flag automatically.

A3. Your account was banned

A banned account sees a clear 🚫 Access Denied message on every command — not silent. If you’re seeing that on /tier or /start, you’ve been suspended. Contact support (@EpicVillages) to appeal — there’s no self-service unban.

B. Specific alerts missing

If some alerts arrive and others don’t, your filters are doing what you configured them to do — usually too strictly. Check in this order; this is the same order the bot’s internal dispatcher runs:

B1. Alert type disabled

The most common missing-alert cause. Each event type (buy, sell, transfer, approval, bridge, NFT, failed, contract interaction) has its own toggle.

Check: Dashboard → Alert Types — confirm the type you expected is enabled. For example, if you expected a transfer alert and the wallet only does transfers, but you toggled “transfers” off at some point, no transfer alert ever fires.

B2. Chain disabled

You can disable specific chains (ETH, BSC, Base, Avalanche, Solana) without un-tracking wallets on them. EVM addresses are tracked across all four EVM chains — if you disabled “BSC” then a swap on BSC for the same address won’t alert, even though a swap on Ethereum will.

Check: Dashboard → Chain Filter — confirm every chain you want alerts from is enabled.

B3. Minimum USD value too high

If you set a min-USD filter, transactions below that value are silently dropped. A $20 swap won’t alert if your minimum is $100.

Check: Dashboard → Notifications → confirm min_usd_value is what you intended. Lower it (or set to 0) to receive everything.

B4. Cluster mode set to “clusters only”

Clusters can be configured in three ways — both, clusters_only, or off. clusters_only mode suppresses individual buy/sell/transfer alerts in favor of the consolidated cluster summary. You only see one alert when 2+ tracked wallets buy the same token within your time window — and you see nothing when only one wallet acts.

Check: Dashboard → Cluster Alerts → confirm the mode is both (or off) if you want individual alerts. EVM and Solana cluster modes are independent — both have their own setting.

B5. Hops-only mode

If you started a hop-tracking session in hops_only mode, regular alerts are suppressed for that wallet — only newly discovered downstream wallets generate alerts.

Check: Send /hops to list active hop sessions. If any are in hops_only mode and you’d rather have all activity, restart them with /hop (without the onlyhop variant).

B6. Hourly rate limit hit

Each tier has an hourly cap (Free: 100/hr, Pro: 1000/hr, Elite: 2000/hr, Exclusive: 3000/hr). When you hit it the bot does notify you — once at 80% used and again at the cap — but if you missed those messages, alerts past the cap are dropped silently for the rest of the hour.

Fix: wait until the next clock hour for the limit to reset. If you hit the cap regularly, upgrade your tier (/upgrade) or trim your tracked-wallet list to lower-traffic wallets.

B7. Subscription is muted for that specific wallet

You can mute a wallet without removing it. Muted wallets still appear in /list but their alerts are silenced.

Check: Dashboard → My Wallets → look for the wallet — if it’s muted, there’ll be a visible muted badge. Toggle notifications back on for it.

B8. The wallet got archived

If you removed a wallet (or were the last subscriber and it auto-archived), it’s no longer in your tracking list. The bot won’t alert for an address it isn’t watching.

Check: /list — is the wallet still there? If not, re-add it with /track <address> <label>. Note that historical activity from before re-tracking is not replayed.

C. Something changed since yesterday

Common transient causes when alerts were working and suddenly aren’t:

C1. Per-wallet throttle kicked in

When a single tracked wallet starts spamming transactions (>15/min), the bot mutes alerts for that specific wallet for 5 → 15 → 60 minutes (escalating with each strike). You’ll get a one-time warning the first time it triggers, then silence.

While throttled, only transactions over $10,000 still alert.

Fix: wait for the throttle to expire, OR set a min-USD filter on your account so the activity stops being noise (Dashboard → Notifications → min USD ≥ $10K), OR remove the spammy wallet (it’s likely a bot, MEV searcher, or hot wallet).

C2. The wallet you’re tracking started routing through a chain you disabled

Same wallet, different chain. If the wallet shifted activity from Ethereum to Base and you have Base disabled, you’ll see “no alerts” even though the wallet is busy.

Fix: Dashboard → Chain Filter → re-enable the chain.

C3. Tier expired in the last 24 hours

Re-read A1. The seven-day warning windows can go unnoticed in a busy Telegram.

D. Telegram delivery issues

If /tier doesn’t even reply, the problem is between the bot and your Telegram client.

D1. You blocked the bot

Open the chat with @reign on Telegram. If you see “Bot was blocked by the user” or no input field, you blocked it (or your Telegram cleaned it up). Unblock the bot and send /start to re-establish the chat.

D2. Telegram rate-limited your chat

Telegram occasionally throttles chats that receive too many messages too fast. If you get hundreds of alerts a day across many wallets, you may hit a temporary 1–24 hour ban on the chat itself — Telegram’s own anti-spam, not ours.

Fix: wait it out. If it happens often, lower your alert volume (raise min-USD, disable chains you don’t trade, or remove low-priority wallets).

D3. Notifications muted in Telegram itself

Tap the chat header in Telegram → check that notifications aren’t muted at the Telegram level. The bot has no visibility into Telegram’s notification settings.

E. Group not getting alerts

Groups have their own filter stack on top of the user’s account state. Check in this order:

E1. The group’s “linked user” has issues

Every linked group has a single user (typically the admin who ran /link) whose account state gates the whole group. If their account is paused, expired-over-limit, or banned, the group goes silent.

Check: the linked user runs /tier and confirms their own state is good. If they hit any account-level issue from section A, the group inherits it.

E2. Group notifications disabled

Open the dashboard → switch to the group’s context (top-left context switcher) → Notifications page → confirm the group itself isn’t muted.

E3. Group-specific chain filter / min USD

Each group has its own chain filter, alert-type toggles, and min-USD setting — separate from your personal ones. Working through B1–B3 above on the group’s settings is the most common fix.

E4. Group rate limit

Groups share the linked user’s hourly alert quota across all their groups. If the linked user has 5 groups and one of them is high-traffic, it can chew through the limit and silence the others.

Fix: linked user upgrades, or some groups need lower-traffic wallets.

E5. Bot was removed from the group

If anyone kicked the bot out, alerts stop because there’s no chat to deliver to. Re-add @reign to the group, then in the group send /link again.

Still stuck?

If you’ve worked through every applicable section and alerts still aren’t firing:

Contact Support Open a chat with the team on Telegram

The team can run a diagnostic that reproduces the dispatcher’s exact filter checks against any specific transaction, so providing the tx hash is the fastest path to an answer.