An error occurred that the bot was not executed.

An error occurred that the trigger event set for the bot was not detected and the bot was not executed.

The configuration of that app is simple:

  1. An action changes the column value from false to true.
  2. A bot detects an event trigger and executes a process.

The bot was not executed even though the column value was correctly changing from false to true.
Most of the bots were executed correctly, but only a few bots were not.

I checked the automation monitor and there was no history of the bot execution.
I don't know the cause, but it seems that the trigger event was not detected.
Audit History was already gone.

Normally, I don't think such errors can happen.
Can anyone think of any reason?

1 6 322
6 REPLIES 6


@AppliSuite wrote:

A bot detects an event trigger and executes a process.


 

Is it a 'Run a data action' in process ? If yes, did you create it directly on a bot ? When you test the bot do you see any errors ? Test just that action from test screen and check if you see any errors.

Did you setup like this ?  Re: Automation Action BUG - Google Cloud Community  

Thank you for replying @Rifad !

The error in my app was not setting the "process".
I thought the trigger "event" was not being detected for some reason.

The bot is triggered by changing the column value from false to true in "Action".
The action was working correctly, but there were a couple of bots that weren't running.
There was no history left in the automation monitor.

I had this error in my customer's app.
It may have been caused by a customer's operation error, but I still thought it was an unusual error.

Thanks for the reference link too.

Try deleting the bot and adding same again. I am not sure about what is causing this issue. For me sometimes redoing or reconnecting works.

Thank you @Rifad !

I can understand your opinion very well.
I don't know what causes this error either.
The user may have done something else while the bot was running...

I can't remove the bot since it's a customer app, but I appreciate your advice.

I think it would be useful to share with the community about the strange phenomenon I experienced.

I understand. I have noticed too. Few actions works properly when triggered manually and does not work when attached to a bot. I have also reported similar issues to support. Hope they come up with a solution.


@Rifad wrote:

Few actions works properly when triggered manually and does not work when attached to a bot. 


I think so.
Therefore, I find this error strange and difficult to pinpoint.

Top Labels in this Space