A community member reported issues with a Typebot automation freezing during a batch test of 170 people. The problem occurred when the automation included OpenAI requests to check users' gender based on their names. Users experienced stalling when trying to proceed through the automation, with the system returning to the "continue" button repeatedly.
Through discussion in the comments, it was revealed that the issue wasn't related to Typebot's server capacity but rather to OpenAI's rate limits, as evidenced by a 429 error (too many requests per minute) in the logs. While specific TPS (Transactions Per Second) information for Typebot Cloud wasn't available, the problem was identified as an OpenAI rate limiting issue rather than a Typebot performance problem.
I recently encountered an issue while processing a batch test of 170 people through a Typebot automation and it froze several times. To better understand and optimize the system, I wonder if anyone can provide information on the system's capacity limitations, specifically in terms of Transactions Per Second (TPS) or any request limits that might be in place? I want to ensure that the system can handle the desired load without encountering performance issues.
This is the video of a user trying to enter his name. Under the name block I had a OpenAi request to check the user gender using the user's name. It would not go through.
In the end of the automation the bot also wouldn't load and the same thing would happen, the user would press "continue" and the automation would stall and go back to the "continue" button
I did, I got a 429 error from OpenAI request, which is the too many request per minute. However, I need to brief the CEO this week and I want to, in addition to showing the error I got from OpenAi, show what are the TPS on typebot servers. Can you provide that information?
