Telegram — Troubleshooting

Error: "Telegram bot not found. Check the bot token"

Message: Telegram bot not found. Check the bot token.

What it means: The Telegram bot token specified in Lightlead's settings is invalid or points to a non-existent bot. The system cannot send the notification.

Possible causes:

• The token was copied incompletely or with extra characters
• The bot was deleted via BotFather
• The token was revoked (reissued) via BotFather
• A token for a different bot, unrelated to Lightlead, is being used

What to do:

1. Open Telegram and go to the chat with @BotFather
2. Send the /mybots command, select the bot in question, then API Token
3. Copy the full token
4. Paste the token into Lightlead's settings ("Integrations" → "Telegram")
5. Save and click "Test connection"
6. Wait for a test message from the bot

Retry the run: yes

Reconnection required: no (only the token)

When to contact support: If the token was copied correctly, but the connection test doesn't pass, or the test message never arrives.

What to send: Error time, screenshot of the error, the token's length (not the token itself!), screenshot of the BotFather screen with the list of bots.

---

Error: "Chat not found. Make sure the user has activated the bot"

Message: Chat not found. Make sure the user has activated the bot.

What it means: Lightlead is trying to send a message to a specific Telegram user, but no chat with this user exists — the bot has never received a /start command from them.

Possible causes:

• The user never pressed Start in the chat with the bot
• The user blocked the bot
• The user's Telegram ID is entered incorrectly
• The bot was restarted, and previous chats were lost

What to do:

1. Ask the user to open the chat with the bot in Telegram
2. Press the Start button (or send the /start command)
3. After that, the bot will be able to send messages to this user
4. Check that the Telegram ID is correct in Lightlead's notification settings
5. Send a test notification

Retry the run: yes

Reconnection required: no

When to contact support: If the user activated the bot and hasn't blocked it, but messages still don't arrive. Or if you need help finding the user's Telegram ID.

What to send: User's Telegram ID (if known), error time, screenshot of the error, screenshot of the user's chat with the bot (confirming /start).

---

Error: "Telegram message limit exceeded. Try again later"

Message: Telegram message limit exceeded. Try again later.

What it means: The bot sent too many messages in a short period and was temporarily rate-limited by the Telegram API. Telegram's limits are approximately 30 messages per second per bot, but can be lower for new bots.

Possible causes:

• Too many notifications are configured to send at once
• Several reports finished at the same time and all sent notifications
• A mass notification was sent to a large number of users
• Telegram applies lower limits to new bots

What to do:

1. Wait 1–5 minutes for the limit to reset
2. Reduce the number of Telegram notifications in the report settings
3. Stagger the report run times so notifications arrive at intervals
4. Combine several notifications into one summary message
5. For large teams — consider alternative channels (email, Slack)

Retry the run: yes (the queue of unsent messages will be processed once the limit clears)

Reconnection required: no

When to contact support: If the limit is exceeded regularly even with a small number of notifications (fewer than 5 per minute).

What to send: Number of active Telegram notifications, number of users receiving notifications, interval between report runs, error time, screenshot of the error.

---

Error: "Failed to send file to Telegram. File size exceeds the allowed limit"

Message: Failed to send file to Telegram. File size exceeds the allowed limit.

What it means: The report file (screenshot, PDF, CSV) that Lightlead is trying to send to Telegram exceeds the Telegram Bot API limit — 50 MB.

Possible causes:

• A report with a large amount of data generates a heavy CSV/XLSX file
• The report includes high-resolution screenshots
• A report covering a long period generates a large volume of data

What to do:

1. Split the report into several with smaller date ranges
2. Exclude charts and screenshots from the Telegram send — keep only a text summary
3. Use Google Sheets as the target source instead of attaching a file in Telegram
4. Set up sending a cloud file link instead of the file itself
5. Reduce the number of metrics in the report

Retry the run: yes

Reconnection required: no

When to contact support: If the file is under 50 MB but the error still occurs, or if sending large files via Telegram is critical for you.

What to send: File size (approximate), file type (CSV/XLSX/PDF/image), number of rows and columns in the report, error time, screenshot of the error.