Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
sunilkumarqv
Specialist II
Specialist II

Qlikview Alert wizard delay not working

Hi Team

We have created a multiple Alerts in Qlik view for business users out of which one alert we need to run at every 48 hours.
Qlikview having inbuilt functionality to perform this activity but we are getting Alert on daily basis. according to this functionality alert should works within 48 hours not 24 hours.

 

Im wondering is this a bug , please provide you inputs Delay.PNG

Labels (4)
1 Solution

Accepted Solutions
peterwh
Creator II
Creator II

Hello,

this is a bug in QV12.20 and it was reported as bug. Here is the answer from Qlik:
"This is a known defect in QlikView November 2017 (12.20), which has been investigated in bugs QV-12778 and QV-15606. These bugs are fixed and the fix will be delivered as part of the QlikView November 2018 (12.30). Resolution: Upgrade to QlikView 12.30 when it is released."

QlikView ignores these settings and the alert fires with every reload.

Whereas "Upgrade to QlikView 12.30 when it is released" was not an option for us, since it was brandnew, when we installed our new QV-farm. So we are using QV12.20 and have to accept this error/bugs (and many more).

Kind regards

Peter

View solution in original post

1 Reply
peterwh
Creator II
Creator II

Hello,

this is a bug in QV12.20 and it was reported as bug. Here is the answer from Qlik:
"This is a known defect in QlikView November 2017 (12.20), which has been investigated in bugs QV-12778 and QV-15606. These bugs are fixed and the fix will be delivered as part of the QlikView November 2018 (12.30). Resolution: Upgrade to QlikView 12.30 when it is released."

QlikView ignores these settings and the alert fires with every reload.

Whereas "Upgrade to QlikView 12.30 when it is released" was not an option for us, since it was brandnew, when we installed our new QV-farm. So we are using QV12.20 and have to accept this error/bugs (and many more).

Kind regards

Peter