Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Knowledge
QlikView 12.10 Multiple Event Trigger change
Article Number: 000028374 | Last Modified: 2018/06/12Description
There is a known potential issue in the QlikView 12.10 track where the Multiple Event trigger functionality may result in the task being triggered running more often than it did in the QlikView 11.20 and 12.00 tracks.
Cause
A piece of logic was mistakenly left out of the rewrite of the QDS in the 12.10 track, whereby the tasks that make up the Multiple Event trigger are not 'grouped' which may lead to the Multiple Event triggered task running at times that are not expected.
Using 'basic' Multiple Event triggers should still perform fine, the issue will likely only occur where the apps making up the trigger app list complete in varying times and the triggered task runs on a fairly constant basis.
An example where the issue will likely occur is where the following task cycle exists:
Task 1 - Multiple Event triggered (3 minute time constraint) (runs in under 1 minute
In the above scenario, what can occur due to the issue, is Task 1, 2 and A as well as B may run out of sync due to Multiple Event trigger not treating Tasks A, B and C as a 'group' and ensuring the entire group has completed within the time constraint configured on the Multiple Event trigger.
Using 'basic' Multiple Event triggers should still perform fine, the issue will likely only occur where the apps making up the trigger app list complete in varying times and the triggered task runs on a fairly constant basis.
An example where the issue will likely occur is where the following task cycle exists:
Task 1 - Multiple Event triggered (3 minute time constraint) (runs in under 1 minute
Task 2 - Triggered on successful completion of Task 1 (runs in under 30 seconds)
Task A - Triggered on successful completion of Task 2 (runs in under 30 seconds)
Task B - Triggered on successful completion of Task 2 (runs in under 1 minute)
Task C - Triggered on successful completion of Task 2 (runs in under 2 minutes)
Task B - Triggered on successful completion of Task 2 (runs in under 1 minute)
Task C - Triggered on successful completion of Task 2 (runs in under 2 minutes)
In the above scenario, what can occur due to the issue, is Task 1, 2 and A as well as B may run out of sync due to Multiple Event trigger not treating Tasks A, B and C as a 'group' and ensuring the entire group has completed within the time constraint configured on the Multiple Event trigger.
Resolution
The issue will be addressed in a future release.
Fixed in 12.10 SR4 and later releases.
Fixed in 12.10 SR4 and later releases.
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us