You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using bot.on('message') to receive updates when a user joins / leaves a supergroup.
Actual Behavior
Sometimes the message update is not received by the bot. This occurs much more often when other bots (especially bot management bots such as Rose) are in the group and remove the join / leave messages. I initially thought the problem could've been caused by the polling mechanism, with other bots removing messages and the update request not containing the deleted messages. I shifted towards websocket but still the error persists.
Steps to reproduce the Behavior
Add a .on('message') event to your bot with a single console log for debug. Add your bot and Rose or Safeguard to a telegram group and try joining and leaving several times.
Feature Request
I have:
searched for such a feature request (
enhancement
) and found none
Introduction
Example
Question
The text was updated successfully, but these errors were encountered:
I have read:
I am using the latest version of the library.
Expected Behavior
I am using bot.on('message') to receive updates when a user joins / leaves a supergroup.
Actual Behavior
Sometimes the message update is not received by the bot. This occurs much more often when other bots (especially bot management bots such as Rose) are in the group and remove the join / leave messages. I initially thought the problem could've been caused by the polling mechanism, with other bots removing messages and the update request not containing the deleted messages. I shifted towards websocket but still the error persists.
Steps to reproduce the Behavior
Add a .on('message') event to your bot with a single console log for debug. Add your bot and Rose or Safeguard to a telegram group and try joining and leaving several times.
I have:
Introduction
Example
The text was updated successfully, but these errors were encountered: