Docs / Monitor / Troubleshooting

Channel Monitor — Troubleshooting

Common issues and how to fix them.

"🚨 Your monitor session has been revoked"

Your Telegram account terminated the Telethon session (manually, by inactivity, or Telegram invalidated it).

Fix: 1. Regenerate the session string locally: python scripts/generate_monitor_session.py 2. DM the bot: /monitor_setup 3. Paste the 3 values (api_id, api_hash, new SESSION_STRING).

"⏳ Flood wait of Xh on your session"

Telegram applied a rate limit to your scraper account. OmniGest pauses reads automatically until it expires.

Fix: do nothing. It resumes on its own.

If you see this repeatedly: - Reduce the number of active sources (/monitor_sources del @X). - Wait a few days and retry. - Consider using a different secondary account.

"⚠ Backlog saturated on @channel"

The source channel published ≥100 messages since the last scrape. OmniGest advanced last_seen_msg_id to the latest processed; some in the middle may have been skipped.

Fix: this is normal for very active sources. If it's persistent and you miss deals, OmniGest's 1h scrape interval is the bottleneck — premium tier will support configurable intervals.

"❌ I'm not a member of {channel}. Add me first and retry."

You forwarded a message from a chat where OmniGest is not a member. Destinations require the bot to be present.

Fix: 1. Add @OmniGest_bot as a member (or admin, depending on the chat type) of the destination. 2. Retry /monitor_dest 1 and forward again.

"❌ That's not a valid forward from a channel or group"

The message you forwarded doesn't have source metadata (Telegram privacy settings hide the forward origin).

Fix: the source chat has "Hide forwarded-from" enabled. Pick a different destination, or ask the chat owner to allow forwarded-from visibility.

"🚫 You don't have access to Channel Monitor"

Your Telegram user id is not in the allowlist. Channel Monitor in Free tier is limited to a specific user.

Fix: contact the OmniGest admin to add your id, or check that you're DMing the bot from the correct account.

No DMs arrive even though the source channel publishes

Checklist:

  1. Flag enabled? Confirm MONITOR_ENABLED=true in .env of bot-referidos.
  2. Session active? DM /monitor_sources list — if the bot replies, handlers are registered.
  3. bot-monitor healthy? On the server: docker logs bot-monitor --tail 20 Look for errors from Telethon.
  4. Poller running? docker logs bot-referidos --tail 20 | grep poll_once Should appear every 3 seconds.
  5. Candidates in DB? sql SELECT status, COUNT(*) FROM monitor_candidates WHERE owner_id=YOUR_ID GROUP BY status; If rows in error, check error_reason.

If candidates exist but the DM never arrives: the URL in the post may not be convertible (not an AliExpress/Amazon link), or your marketplace filter excludes it.

The affiliate URL conversion may have failed. Check:

  1. /afiliado credentials still valid (your AliExpress or Amazon tag not expired).
  2. Click a freshly published link to verify it redirects to the correct product page with your tag in the URL parameters.

If the link is broken, the candidate's error_reason will explain. Transient errors are retried automatically (max 3 times).

First scrape doesn't happen

The first scrape runs 1 hour after bot-monitor starts. If you just deployed the feature and waited less than that, you're fine — check back later.

To force an immediate scrape (admin only, VPS access):

docker exec bot-monitor python -c "
import asyncio; from bot.monitor.runner import scrape_all_owners
asyncio.run(scrape_all_owners())
"

Still stuck?

Contact support with: - Your Telegram user id. - The exact command or action that fails. - The error message you see (if any).