My "Incoming Messages & Events" credits are being ...
# 🤝help
l
Hey, I've buit a bot for I client in November and since then they had been using it without any inconveniences. However, in the last few weeks, we suddenly ran out of Incoming Messages & Events credits. I bought 5000 more credits only to find out they got consumed overnight. However, when checking the analytics I didn't have more than a few messages over that period. I made some changes and bought 10k more but they also got consumed overnight. I'll share with you the analytics from January and from last night. In January it worked perfectly fine and we didn't change anything in our end. Can you think of any solution for this? I've spent over $30 in the last 72 hours 😦
c
Hello! Do you have any kind of triggers? Are you using gpt4? I'd recommend using the Hybrid mode.
f
You can check the logs for your chatbot where you can see why it got triggered. I can think of some possibilities here but a screenshot of the logs would help clarify why it consumes so many Messages
l
I do have a trigger. here is a screenshot of the logs
I can send you a larger portion of the logs if needed
I'm not using GPT-4 nor any other AI function
f
Can you take a screenshot of your timeout workflow
l
it's the default one I think
f
That is the problem
It never stops even though the user has stopped responding
You don't want to continue the flow like that
You want it to end when the user stops typing for x amount of times
You could create a bit of logic to maybe go to that workflow once when the user timeout and then the next time it would end the chat.
l
Ohh okay. So where should I add the logic? In the timeout workflow? I don't mind killing the run if they time out for more than let's say 10 mins.
f
You can set the amount of minutes before the timeout in the settings fo the bot
Then just go straight to the end node in the Timeout workflow
You could add a Text card in the timeout workflow to let the user know they have timeout, but you should not use a capture information card as it will reset the timeout.
l
Cool thanks! I'll let you know if this works
c
Please keep us posted.
Thanks @fresh-fireman-491
f
You are both very welcome
l
Seems to be working fine now. Thanks!
f
That's amazing to hear!
106 Views