If it’s triggered more than once, that you can eliminate if you check that at least from the Audit history. It shows if it’s triggered manually or with the schedule. From the Audit history you could probably see more reasons what it could be. Any chance you have two Bots doing the same thing.. one data change and one scheduled. Just trying to think what the reason could be other than a bug.
When the scheduled Bot is triggered, is the 2nd one triggered always and is this happening always 5 minutes later? What kind of Bot is it? Does it need to wait a condition, duration, etc.?
Hello Aleksi. There’s no condition. It is just a scheduled bot that will run every 1PM UTC (9AM EST) and my client doesn’t run it manually. Does updating record will trigger the scheduled bots?
If that logs belongs to your scheduled Bot, it seems that it is triggered several times in a day. Please take a printscreen from the Audit history, not from the Automation monitor.
No worries. If you open both of these logs, you are able to see from the details if it’s triggered with the schedule or with manually. Please check that next.
The only time I’ve had something like this happen is when I launched the bot manually, and the script timed out because it reached the execution time limit. Seemingly when this happened, the bot launched again, however I manually terminated the script rather than waiting to see if the bot continually repeats.
Everything seems to be just fine. Both are triggered by the schedule, not manually. It’s the EventType detail that shows it. To investigate more, I would need to have access to your app. If you want that, please send me a PM.
Thank you for your reply! I think our app is timing out too. We moved the bot to another app (with just few tables unlike the main app) and it’s now fixed!
Hello Aleksi. Thank you for your help! We already solved the problem by creating another app (with just few tables unlike the main app) to run the scheduled bots
My daily bot is also being triggered multiple times a day. With about a 10 minute succession it runs three times. It does have a trigger formula with select() that has to read through a large file. How can I prevent it from timing out? De bot does function correctly, only to many times.
One workaround is to create a slice that filters the data amount and then if you run the Bot against that slice, the 5 minutes limitation may not be exceded.