Qlik Alerting any limit on number of data alerts?

[dvugopietro]

Hello. I have an installation of Qlik Alerting on premise (not on cloud) linked to a Qlik Sense envinronment on premise.

I noticed that some data alerts are not scanned by the Qlik alerting engine when the qlik sense app is being reloaded (they are correctly set).

I have more than 110 data alerts activated on 1 user and on 1 appliation.

Is there any limitations on the number of data alerts that can be scanned and potentially triggered?

Thank you for your response,

[JavierL]

Same here, alerting on premise with sense may 2025 patch 2, it only scans 100 alerts configured with 2 users and then stops (it should be doing around 250 scans) it completes about 60 for 1 user and about 40 for the other one in 15-20 minutes and then completely stops

[JavierL]

Hey, i figured it out on my own im going to try to explain it, its not clean, there should be an easier way to do it, such a setting panel in the web interface for admins, but it works

C:\Program Files\Qlik Alerting\setup\db\upgraders file conditionAndDataHistory contains parameter $limit=100, change it also index file, same route.

Also "server" file from C:\Program Files\Qlik Alerting\repository search for "limit:100" and change it

Just in case i also modified timeout setting in C:\Program Files\Qlik Alerting\qlik-connector\config 

Modified C:\Program Files\Qlik Alerting\worker\config to increase number of parallel workers so it would take less time to scan.

Also in C:\Program Files\Qlik Alerting\email-messenger\config i modified the number of max concurrent email sent to avoid the email server (outlook) to discard them when it goes above 3 at the same time

Hope that helps if someone is still stuck with something similar

[mrsimon007]

There isn’t a strict published limit on the number of data alerts in Qlik Alerting, but performance issues can appear when you have a very high volume, like 100+ alerts tied to a single user or app. The engine may skip some alerts during reloads if resources are stretched. Think of it like using tools such as DelttaExecutor, where too many processes at once can cause instability — spreading alerts across apps or users usually helps.