Summary:
The bot connected to the Bot API sends events to different topics in a group chat. However, after a while, it stops working, and we need to create a new topic to resume functionality. It appears that the topic ID length increases each time it stops working, and only after creating a new topic with an increased ID does it start working again.
Steps to Reproduce:
Set up a bot that sends events to different topics in a group chat.Monitor the bot's activity as it functions.After a period of normal activity, the bot stops sending events to the topics.Attempt to resume by using the same topic ID—this fails.Create a new topic to continue, and the bot resumes working, but with an increased topic ID.
Example Behavior:
Previous Topic ID: 1012744New Topic ID (after bot stops working): 2069941
Expected Behavior:
The bot should continue sending events to the existing topic without needing to create a new one or seeing an increase in the topic ID length.
Observed Behavior:
The bot stops functioning intermittently and only works again after a new topic with an increased ID length is created.
Additional Information:
The issue seems to be linked to the increasing length of the topic ID each time the bot stops functioning.
Request:
Please investigate and resolve this issue, as it appears to be a bug in the Bot API's backend that prevents the bot from consistently sending events to group chat topics.
Thank you for your attention to this matter.
Steps to reproduce
Example Behavior:
Previous Topic ID: 1012744New Topic ID (after bot stops working): 2069941
Expected Behavior:
The bot should continue sending events to the existing topic without needing to create a new one or seeing an increase in the topic ID length.
Observed Behavior:
The bot stops functioning intermittently and only works again after a new topic with an increased ID length is created.
Device info
Its on bot api no matter what the os version or device model is
The problem is releated to supergroup limits of 1M messages, after 1M old topic created can be unavailable or partially unavailable and bot api has problem with that