I have a scheduled bot that fails to run automatically at its designated time. It operates correctly when triggered manually. The app is deployed, my account is on a core plan, and there are no security filters in place. Do you have any suggestions on what might be wrong?
Have you checked the automation log to see if your filter condition returned any rows and/or if the bot failed due to an error?
Yes, I have. Is it something wrong?
the result using the existing formula:
the result using a "True" expression:
OK.
One issue with bots is that they have a task timeout of 120 seconds.
The monitoring app does not report an error when the bots fails because of a timeout, unless it's because of a script called and running for too long for example.
Do you think the volume of rows to consider for your bot may be the cause of the situation?
If so, you may want to consider running the bot on a slice rather than the entire table, and maybe running separate bots for separate slices to achieve your goal.
Strangely, there is only one entry in the table. I also created a bot for another table with the same flow, but the bot still doesn't work automatically. Could there be a restriction on workspace account settings?
Strange indeed, I don't think any restriction would be the cause of your situation.
You may want to file a ticket. Can you keep us updated so that we know how to avoid this later?
I just tried creating a new app with a simple table structure, but the result remains the same. The bot still doesn't work.
How do I file a ticket?
Thanks. I will keep you updated
User | Count |
---|---|
21 | |
15 | |
4 | |
3 | |
3 |