Troubleshooting
The bot doesn’t reply to a command
Section titled “The bot doesn’t reply to a command”| Cause | Fix |
|---|---|
| Someone ran the same command in the last 10 seconds | Your message was deleted on purpose. Scroll up for the answer. |
| The bot isn’t set up in this group | An admin sends /config |
| The bot is switched off | An admin turns it on in /config → ⚙️ Server |
You sent $TICKER for a token this group doesn’t track |
Use a tracked ticker, or /liquidity $TICKER for any token the bot knows |
A command replies “…is for Mosh launches”
Section titled “A command replies “…is for Mosh launches””The group only tracks regular tokens, and the command needs a Mosh launch. /price, /holders, /liquidity, /burn and /card still work. Admins can show or hide Mosh commands in /config → ⚙️ Server → 🧩 Mosh commands.
Setup problems
Section titled “Setup problems”“Admins only.” You need to be an admin of the group.
“Please turn off ‘Remain anonymous’ in your admin rights to configure the bot.” The bot can’t verify an anonymous admin. Turn it off in the group’s admin settings while you set up.
“Setup has moved to DM: send /config” You pressed a button from an old setup menu in the group. Send /config again.
“⌛ Setup expired, please start again.” The setup wizard timed out. Start again from /config.
“📬 I can’t DM you yet.” Open @BundlePepeBot, press Start, then run the command again.
Contract address errors
Section titled “Contract address errors”| Message | What it means |
|---|---|
| Not a valid 0x address | The address should be 0x followed by 40 characters. Copy it again. |
| Address checksum is invalid | A character was changed. Copy the full address again. |
| No contract code at this address on Robinhood Chain | Wrong network, or a wallet address instead of a contract |
| This contract does not look like a Mosh bundle | You pasted something that isn’t a Mosh bundle. For a regular token, use 🟢 Robinhood Coins instead. |
| That address isn’t an ERC-20 token on Robinhood Chain | The address isn’t a token |
| This bundle’s contract raises in X, so Y can’t be used | Pick the currency the bundle actually raises in |
Buy Settings errors
Section titled “Buy Settings errors”| Message | What to do |
|---|---|
| This group can track N token(s) | Remove a token first (🟢 Buy Settings → token → 🗑 Remove) |
| Too many token changes in the last hour | A group can add 6 tokens per hour. Wait and try again. |
| Buy alerts are at capacity right now | The bot is watching as many tokens as it can. The team has been told. |
| Send an amount in USD, like 25, 0.5 or 1.5k | Type a number. k and m work. |
| Send a single emoji | One emoji only |
| Just scanned. Try again in a minute | Pool scans run at most once a minute |
| Telegram wouldn’t treat that file as a video | Use MP4. Files must be 20 MB or less. |
A buy didn’t post
Section titled “A buy didn’t post”Check, in order:
- Was it under the minimum? Default $10. See 🟢 Buy Settings.
- Was it a sell? Sell alerts are off by default.
- Was it a round trip, arbitrage or a routing hop? These are skipped on purpose.
- Was it an agent? If the group gets agent alerts for that wallet, the trade appears as an agent alert instead.
- Was it on a new pool? Pools count once they have about $500 of liquidity or 20+ swaps a day. An admin can run 🔍 Scan for new pools. If none qualify, the bot says no tradable pools found yet.
- Were there several buys at once? More than 4 buys in 10 seconds are combined into one post.
Funding alerts stopped
Section titled “Funding alerts stopped”Funding alerts switch off by design when the bundle graduates. You’ll get agent and buy alerts from then on.
Data errors
Section titled “Data errors”| Message | What to do |
|---|---|
| mosh.trade is unavailable right now | mosh.trade didn’t respond. Try again shortly. |
| Couldn’t read the price / pools / fee data right now | A data source didn’t respond. Try again in a minute. |
| No price yet: no trades found for this token | The token hasn’t traded yet |
| Building holder history for $SYM | First /holders for a busy token. Try again in a few minutes. |
| The Mosh report isn’t ready yet | Digests are built after 00:00 UTC. Try again in a few minutes. |
| One wallet check every few seconds, please | Wait 10 seconds between wallet lookups |
Alerts go to the wrong place
Section titled “Alerts go to the wrong place”- In a forum group, alerts go to the topic set with
/settopic. If that topic was deleted, they go to the main chat. Send/settopicin the topic you want. - On Discord, alerts go to the 📍 Alert Channel set in
/config.
Discord link errors
Section titled “Discord link errors”| Message | What to do |
|---|---|
| That code is invalid or expired | Codes last 10 minutes. Run /link on the other side for a new one. |
| That code belongs to this same group | Use the code on the other platform |
| Link a Telegram group with a Discord server | You can’t link two Telegram groups or two Discord servers |
| One of them is already linked to something else | Run /unlink there first |
Still stuck?
Section titled “Still stuck?”Ask in the Bundle Pepe Telegram group. Include the group name, the command you sent, and the exact reply.