Troubleshooting

Quick solutions to common issues and problems with MoBots Buy Bot. Find answers to setup problems, notification issues, and configuration challenges.

Problem: Bot can't find any liquidity pools for your token.

Possible Causes:

• Token doesn't have liquidity yet
• Token not paired with MON/WMON
• Incorrect token address
• Liquidity on unsupported DEX

Problem: Your Telegram group doesn't appear when creating a bot.

Possible Causes:

• Bot not added to group yet
• You're not admin in the group
• Bot cache needs refresh
• Group removed bot

1. Verify Bot is in Group

   • Open your Telegram group
   • Check members list
   • Look for @MobotsBuyBot
   • If not there, add it

2. Confirm Admin Status

   • Go to group → Administrators
   • Verify you're listed as admin
   • Must have admin rights to create bot

3. Refresh Bot List

   • In bot chat, click "🔄 Refresh List"
   • Waits for cache update
   • Group should appear

4. Re-add Bot if Needed

   • Remove bot from group
   • Add it back
   • Make it admin
   • Check list again

Problem: Bot is configured but notifications aren't appearing.

Most Common Causes:

• Bot not admin in group
• Bot deactivated
• Minimum amount too high
• No qualifying buys yet

1. Check Bot Status

Go to: My Buy Bots → Select Group
Look for: Active 🟢 (not Inactive 🔴)
Action: If inactive, click "🟢 Activate"

2. Verify Admin Permissions

Open Group → Administrators
Find: @MobotsBuyBot in list
Check: "Post Messages" permission enabled
Action: If not admin, add it as admin

3. Test Minimum Amount

Current Setting: Check "💰 Set Minimum Amount"
Action: Temporarily set to 0
Test: Make small buy to verify
Reset: Adjust back to desired minimum

4. Confirm Buy Activity

Check: Recent buys on Dexscreener
Verify: Buys are actually happening
Ensure: Buys meet minimum threshold
Test: Make test buy yourself

Problem: Buy amounts, prices, or other data looks incorrect.

Possible Causes:

• Token has non-standard decimals
• Contract reports wrong information
• Display precision issue
• Pool liquidity imbalance

1. Verify on Explorer

   • Click transaction link in notification
   • Check actual token transfer amounts
   • Compare with notification

2. Check Token Decimals

   • View token on Monad Explorer
   • Verify decimals() function returns correct value
   • Standard is 18, but can vary

3. Cross-Reference Dexscreener

   • Click DEX link in notification
   • Compare buy size on Dexscreener
   • Should match within precision

4. Report Persistent Issues

   • If consistently wrong, contact support
   • Provide token address
   • Include example transaction hash
   • May be token contract issue

Problem: Notifications show "DEX: Unknown" instead of specific DEX name.

Possible Causes:

• Old bot configuration (before DEX ID feature)
• Unsupported DEX
• Factory contract misconfigured
• Pool not from standard factory

For Old Configurations:

1. Go to "🔄 Change Token/Pool"
2. Re-enter your token address
3. Select pools again
4. New buys will show correct DEX

For Unsupported DEXes:

1. Contact MoBots support
2. Provide DEX name and website
3. Request DEX to be added
4. Future update will include it

For Custom Pools:

• If pool not from standard factory, may show Unknown
• Bot still tracks correctly
• Just can't identify specific DEX

Problem: Uploaded image doesn't show in buy notifications.

Possible Causes:

• Image URL is broken
• Image too large (>5MB)
• Invalid image format
• Telegram blocked image
• Network issue during upload

1. Re-upload Image

   • Go to "🖼️ Change Image"
   • Upload image directly (don't use URL)
   • Keep file under 5MB
   • Use PNG or JPG format

2. Verify Image Format

   • Must be PNG or JPG
   • Square dimensions recommended (1:1 ratio)
   • Not animated GIF
   • Not WebP or other formats

3. Test Different Image

   • Try simple, small image first
   • If works, issue was with original
   • Resize/optimize original and retry

4. Check URL if Using Links

   • Must start with http:// or https://
   • Must be publicly accessible
   • Test URL in browser first
   • Use direct image link, not webpage

Problem: Added social links but they don't appear in notifications.

Possible Causes:

• Links not saved properly
• Incorrect format
• Telegram blocking malformed URLs

Verify Links Saved:

1. Go to "🔗 Social Links"
2. Check for ✅ next to each platform
3. If ❌ shown, link not saved
4. Re-enter links

Check Format:

✅ Good Formats:
Discord: https://discord.gg/yourserver
Telegram: https://t.me/yourgroup or @yourgroup
Twitter: https://twitter.com/yourhandle
Website: https://yourproject.com

❌ Bad Formats:
discord.gg/server (missing https://)
t.me/group (missing https:// unless using @)
@handle for Twitter (use full URL)
yourproject.com (missing https://)

Re-add Links:

1. Click platform button
2. Send correctly formatted link
3. Wait for confirmation
4. Test with new buy notification

Problem: Can't create new bot because limit reached.

Cause: Free tier allows maximum 2 bots per user.

Option 1: Delete Unused Bot

1. Go to "🤖 My Buy Bots"
2. Select bot to remove
3. Click "❌ Delete Bot"
4. Confirm deletion
5. Create new bot in freed slot

Option 2: Deactivate Instead

• If you might need bot later, deactivate it
• Keeps settings but stops notifications
• Doesn't free up bot slot though

Option 3: Reconfigure Existing Bot

• Change token/pool on existing bot
• Reuse slot for new project
• Faster than delete/recreate

⚠️ Remember: Deleting a bot is permanent. All settings, image, and social links will be lost.

Problem: Can't add bot to Telegram group.

Possible Causes:

• Group privacy settings
• Not an admin
• Group full
• Bot blocked

1. Check Group Settings

   • Group → Edit → Group Type
   • If Private, ensure you're admin
   • If Public, should allow bots

2. Verify Admin Status

   • You must be admin to add bots
   • Check Administrators list
   • Need "Add New Admins" permission

3. Try Different Method

   • Method A: Group → Add Members → @MobotsBuyBot
   • Method B: Share group link with bot
   • Method C: Forward message from bot to group

4. Check Group Capacity

   • Standard groups: 200k members
   • If near limit, might have issues
   • Unlikely but possible

Problem: Worried about other admins changing bot configuration.

Actually Not a Problem: Only the creator can manage bot settings.

Creator Permissions (You):

• ✅ Change token/pools
• ✅ Update image
• ✅ Set minimum amount
• ✅ Manage social links
• ✅ Activate/deactivate
• ✅ Delete bot

Other Admin Permissions:

• ❌ Cannot access bot settings
• ❌ Cannot modify configuration
• ❌ Cannot delete bot
• ✅ Can only see notifications (like everyone else)

Security: Only your Telegram user ID can manage the bot.

Problem: Can't complete bot setup when "Remain Anonymous" is enabled.

Cause: Anonymous mode hides your user ID, preventing creator registration.

1. Temporarily Disable Anonymous Mode

   • Group → Edit
   • Administrators → Your Name
   • Turn OFF "Remain Anonymous"

2. Complete Bot Setup

   • Add bot to group
   • Make it admin
   • Configure in private chat
   • Verify notifications work

3. Re-enable Anonymous Mode

   • After setup complete
   • Group → Edit → Administrators
   • Turn ON "Remain Anonymous"
   • Bot continues working normally

Problem: Notifications arrive several seconds/minutes after buy.

Possible Causes:

• Network congestion
• High block time variance
• Telegram delivery delay
• Bot processing queue

Normal:

• 2-10 seconds after transaction confirms
• Monad block time: ~1 second
• Bot check interval: 2 seconds
• Processing: 1-2 seconds
• Telegram delivery: 1-5 seconds

If Longer:

• Check Monad network status
• Verify transaction confirmed on explorer
• Check Telegram connection
• Usually resolves automatically

Issue: No Notifications

Check in order:

1. Bot status Active 🟢? If not, activate
2. Bot is admin? If not, make admin
3. Minimum too high? Lower to 0 to test
4. Any recent buys? Check Dexscreener
5. Test buy yourself? Make small purchase

Issue: Wrong Information

Check in order:

1. Verify on Monad Explorer (click tx link)
2. Cross-check on Dexscreener
3. Check token decimals on contract
4. Report if consistently incorrect

Issue: Can't Setup

Check in order:

1. Token address correct? Verify on explorer
2. Pools exist? Check Dexscreener
3. Bot added to group? Check members
4. You are admin? Check administrators
5. Anonymous mode? Disable temporarily

If problems persist after trying these solutions:

1. Join MoBots Community

   • Get help from support team
   • Ask other users
   • Report bugs

2. Provide Details When Asking for Help

   • Token contract address
   • Group name (if comfortable sharing)
   • Specific error messages
   • Steps you've already tried
   • Screenshots if applicable

3. Check for Updates

   • Bot might have maintenance scheduled
   • New features might affect configuration
   • Follow MoBots announcements