Triggered automations will require their Run Mode to be set to triggered to continue to work as expected. Past January 13th, it will no longer be possible to use the below endpoint to trigger an automation not explicitly configured with a triggered run mode:
api/v1/automations/{id}/actions/execute
How do I configure the Run Mode?
The run mode can be configured in the Start block of an automation:
Open the Automation
Select the Start Block
Open the Inputs tab
Select Triggered as the Run Mode
Additional change: Execution tokens become header parameters (February 1st, 2026)
An additional change to how execution tokens are used will be introduced on February 1st, 2026.
When triggering a triggered automation through the trigger URL (see the endpoint below), the execution token must be sent as a header parameter. Currently, it is possible to send the execution token as a query parameter. Starting February 1st, 2026, sending execution tokens as header parameters will be enforced.
api/v1/automations/{id}/actions/execute
Related improvement: custom parameter support for button-triggered automations
When triggering an automation from a button in an app it is now possible to provide additional input parameters that are defined in the button configuration. More information can be found here: custom input parameters for the native button.
Don't hesitate to reach out if you have any questions or address our experts directly in the Qlik Application Automation forum.