Skip to main content
Announcements
Global Transformation Awards submissions are open! SUBMIT YOUR STORY
Sonja_Bauernfeind
Digital Support
Digital Support

Hello Qlik Users,

 

On January 13th 2025, Qlik will introduce breaking changes to the execution token functionality for triggered automations. 

Contents

 

What does this mean for my triggered automation?

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:

  1. Open the Automation
  2. Select the Start Block
  3. Open the Inputs tab
  4. Select Triggered as the Run Mode

    set run mode.png

Additional change: Execution tokens become header parameters (Q2 2025) 

An additional change to how execution tokens are used will be introduced at a later date. The change is planned for Q2 2025

When triggering a triggered automation through the trigger URL (see the below endpoint) the execution token must be sent as a header parameter. Currently, it is possible to send the execution token as a query parameter. With Q2 2025, sending execution tokens as header parameters will eventually 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.

 

Thank you for choosing Qlik,
Qlik Support

5 Comments