Automation no longer started (invalid request) by button in app

[coengiesberts_anva]

One of my apps that I have deployed onto 40 tenants, uses buttons to launch automations. Since recently the buttons that launch automations stopped working on SOME tenants.

At this point in time, on some tenants the buttons are still working and on some tenants they NO longer work:

* some existing tenants allow the automation with run mode manual to be launched by a button
* Some recently deployed tenants that execute automations with run mode manual  return an error "invalid request" when executed by the button. changing the run mode from manual to triggered allows the automations to be executed in these cases.

How come this behaviour is different from tenant to tenant? Why do I have to change the run mode on some tenants, while on other (older) tenants all settings can remain unchanged?

[Shai_E]

Hi @coengiesberts_anva 

* Some recently deployed tenants that execute automations with run mode manual  return an error "invalid request" when executed by the button. changing the run mode from manual to triggered allows the automations to be executed in these cases.|

For these tenants, what do you have configured for the button that runs the automations through the app?

Is the run mode triggered ticked?

If it is ticked in the button action settings it makes sense why it will only run the automation if its run mode is triggered.

The logic behind this is that if you tick triggered mode in the button, it can only run the automation if it has a triggered URL created for it with an execution token.

If the automation was in manual mode that means we are not allowing anyone to run it.

Triggered mode means that if a user has the execution token along with the trigger URL, any user can run the same automation.

Assuming the above is your use case

Best Regards