The community members have identified a bug in a bot that causes it to initiate a second flow in the middle of the first one, duplicating all messages. This issue seems to occur only when there is a prolonged gap between user interactions. The community members have explored this bug by creating their own bot and testing it on WhatsApp and the web version. They have found that the issue occurs on WhatsApp, especially when there are many messages or a long delay between them, but not on the web version.
The community members have discussed potential solutions, including migrating from a serverless environment and increasing the timeout. However, the migration is an important change that cannot be rushed, and the community members are actively working on it. The expected deployment is in a week or in February, but one community member has a strict deadline and may need to consider other options.
In certain situations (I'm not sure about the specific conditions yet), when interacting with the bot through WhatsApp, the bot initiates a second flow in the middle of the first one, duplicating all messages. At first glance, it appears that this issue occurs only when there is a prolonged gap between user interactions.
It seems to be working, of course such a small waiting time can have big changes, it depends on processing, networking and communication between applications
Thank you! Do you have an expected due date for this? I really don't mean to rush you; I'm just asking because I have a very strict deadline to present a MVP to the big guys, and without this fix, I should probably juts pull it off already.