BOT not getting triggered

jyothis_m · 08-18-2023 01:12 AM

Is anyone else facing issue of BOT not getting triggered even though the condition is met. Observed this in some BOTs starting yesterday.

jyothis_m

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.

AleksiAlkio

Have you checked what it shows in Audit history for the reason why it's not triggered?

jyothis_m

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

AleksiAlkio

Do you have any other condition rule than just the 5min delay?

jyothis_m

No other condition. All these BOTs were running fine till previous day and i have not made any changes to them recently.

AleksiAlkio

Better to file a support ticket.

jyothis_m

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.

AleksiAlkio

Yes, it could be.

jyothis_m

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

jyothis_m

Reply from Support : As confirmed from the specialist team this is a known issue and the specialist team working on the same on priority.

1minManager

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

jyothis_m

Most probably its connected with the same update that caused the issue in my bots

1minManager

Reported to Appsheet Devs directly

jyothis_m

How can the issues be reported to devs. Is it the support chat/email which you are referring to.

Michael_at_Graz

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.

Michael_at_Graz

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.

Daisy_Ramirez

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.

Brian93

Any news?
Have the same problem.

jyothis_m

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.

jyothis_m

No update from support team yet. BOTs are still stuck in WAIT step

Daisy_Ramirez

Same here. @jyothis_m Sorry to report we've been dealing with this sporadically for weeks with no response. I believe it's been since early July. The que does clear up and we thought the issue was resolved but the issue will happen again if an update isn't implemented. With the disruption to the operation, we've removed the Wait condition and will look to work around it. I'm messaging to hopefully save you the time we expended on this one:)

jyothis_m

Thank you 😊 @Daisy_Ramirez

Michael_at_Graz

Looks like appsheet fixed something. i dont get a new info from support, but our scheduled bots, triggered by condition, that send notification, got working till today morning.

jyothis_m

I think the issue is not resolved yet. Some of the previous pending bots have now completed. But still new instances of Bots triggered even now are getting stuck at wait step even after 15 mints though the wait period is just 5 mints.

jyothis_m

recent instance of BOT with wait step of 5 minutes. Took about 90 minutes for it to get complete.

Mauricio_Bick

Not fixed yet. Hopefully it gets fixed soon because I’m really counting on bots to get a lot of things done.

jyothis_m

Today's result was ok. BOT continued after 5 minutes delay. May be its fixed now. No confirmation from support yet.

Koichi_Tsuji

@jyothis_m wrote:

No confirmation from support yet.

hmmmm.....😯

Rifad

@Daisy_Ramirez wrote:

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.

This is the biggest major problem we face everyday. The keep dragging a minor issue weeks and even months.

jyothis_m

Reply from Appsheet Support received today

jyothis_m

The issue has reappeared. All BOTs with WAIT step are pending even after several hours