API vs GUI Bot triggering issue

[mustafa1]

Hi,

There is a difference in automation depending on how the action is triggered.

When a bot is triggered via App or Web GUI, the action run by that BOT does not trigger another  BOT.

But when I trigger the same BOT via API call. The action run by that BOT triggers a new BOT.

If I visualize

GUI-> Triggers BOT"->Action. (Stops here)  BOT2 

API->Triggers BOT 1->Action -> Triggers BOT2

Am I missing something? I think both should act the same?

[jyothis_m]

I remember that there is an option available in BOT settings to enable/disable other BOTs that listen to the data change made by this BOT. Pls check it out. 

[mustafa1]

But this is the same BOT. Difference is triggering source.

[mustafa1 · Accepted solution]

I think I found the problem.
The data change action triggering BOT2 is also embedded in the save action. For that reason, the action is fired by BOT1 but does not change anything and does not trigger the BOT through GUI.
But when it is run through API, since the save button is not pressed,  the action really changes something and fires BOT2