Is anyone else facing issue of BOT not getting triggered even though the condition is met. Observed this in some BOTs starting yesterday.
1 Like
I have 3 BOTs which get triggered by the same Data change event and have the same condition for triggering. But only one of them is getting triggered. Other two BOTs are not triggered at all and not even showing in Automation Monitor. It was working fine till yesterday.
Have you checked what it shows in Audit history for the reason why it’s not triggered?
1 Like
Yes. in Audit History its showing Condition: false but the condition is same for all the 3 BOTs.
One more thing that I found is that several of the BOTs which have delay step (5 mints) in them have not continued after that step. All are showing status as pending with reason SUSPENDED_ON_CONDITION
Is there a chance that since several BOTs are in suspended states, some timer limits are exceeded or something like that. Because its weird that the BOTs are pending from 17/08/2023 04:31:01 UTC
Do you have any other condition rule than just the 5min delay?
1 Like
No other condition. All these BOTs were running fine till previous day and i have not made any changes to them recently.
Better to file a support ticket.
1 Like
Yes. I have also created a test app with just a single BOT with WAIT of 5 mints in between. That is also pending even after 20 mints.
I think the WAIT element is causing some trouble, may be after a recent update by appsheet team.
1 Like
Yes, it could be.
1 Like
Reply from Support : As confirmed from the specialist team this is a known issue and the specialist team working on the same on priority.
1 Like
Possibly linked. But I have an app that has various bots on schedules. They are all sudenly failing on RequiredIF issues where that formula is:
ANY(Select(Staff[Type],[Login Email]=UserEmail()))="Admin"
Since these are bots there is no UserEmail() so the result cannot be “Admin”. Yet the result of the formula is acting like it is “admin”. For now I’ll add:
CONTEXT("Host")="Server"
But it seems to me to be an Appsheet update has cause this as this part of the app hasn’t changed in weeks.
Simon,1minManager.com
1 Like
Most probably its connected with the same update that caused the issue in my bots
1 Like
Reported to Appsheet Devs directly
2 Likes
How can the issues be reported to devs. Is it the support chat/email which you are referring to.
1 Like
i have the same problem. scheduled bots get not triggered and also bots with data change get not triggered. monitor tell everything is complete, but nothing happend. fells like we are beta tester for appsheet bots…
anyway, i have report this problem to appsheet support this morning at around 08:00 am GMT +2, but till now, i only get the info that they are working on it.
1 Like
Try if it works now, cause my bots, getting triggered from data change works now. they also stopped working from yesterday till today. seems appsheet fixed something.
Been reporting this for weeks and response is “it’s being escalated” but no resolution or dialogue on the issue for weeks - major disruption to client operations.
2 Likes
Any news?
Have the same problem.
The issue is still not resolved. Another major thing that is getting affected due to this is that the same BOT is not getting triggered again if the previous instance is in WAIT (still pending) and the BOT is triggered by another event. It does not even appear in Automation Monitor. However in Audit Log it is appearing with Result as Condition: False but while viewing the detail, there is no condition at all.
