The community members are experiencing issues with their self-hosted Typebot bot, version 2.28.2, where some flows that used to work have stopped working without any changes to the bot. The filter component in some tasks has stopped working, causing the flow to "die" when it reaches this component. The community members have noticed this behavior in two cases, one of which was a critical incident where the bot stopped working for all customers. They have checked the server logs and API calls, but could not find any errors. In one case, they were able to fix the issue by recreating the condition component, but they still have one task that they had to disable for customers as they could not fix it. The community members are seeking guidance on how to investigate and fix this issue.
The comments suggest that the issue might be caused by an infinite loop or something getting stuck in the condition component. The community members are advised to add Wait blocks with the "Pause the flow" option set before each HTTP request block and each link to Typebot blocks to help investigate and potentially resolve the issue.
Flows that used to work stopped without any changes in the bot. In the last few days our bot stopped working normally. There wasn't any change in the bot that explain this behavior. We have a self-hosted Typebot, version 2.28.2, same version since September and we observe that the filter component, in some tasks, stopped working and the flow "dies" when arrives in this specific component. I can send you a DM with a video attached showing step by step of a flow that was working since September.
We have noticed this behavior in two cases, onde critical happened today, where created an incident where the bot stopped working for all customers. We didn't have any changes in the bot, one flow stopped to work properly and impacted many customers. We had to disconnect the entire flow to keep the bot available for customers, but we still haven't found any explanation for this specific behavior and error.
Please, guide us on how to investigate or fix this issue. Thank you
If you didn't touch anything and it used to work then I can only think of one of your API that changed? Since it seems you are doing a lot of HTTP requests
Yes, we couldn't find any error in the logs! The APIs are normal. This error happened in 2 tasks. One task we still have a problem, the other task I could fix simply by "recreating the component". I tracked each step and noticed that the bot "broke" at a condition component. I deleted that component and added new "condition" component, creating the same filter and then this task worked again. We still have one task, that we disabled for customers, that even recreating the component we could fix it.
Is there any tip or method that we could investigate more?
