Creating an alert

Creates an alert that emails a group of recipients automatically whenever the Qlik event you’re watching happens - independent of any report.

Prerequisite

You need at least one connected Qlik server (see Connect Qlik Sense) and a recipient group to notify (see Recipients & groups).

Steps

1. Go to Alerts in the sidebar and select New alert.

   

2. Choose what to watch - a Qlik task reload, a report’s execution, or a Qlik Cloud app reload - and either pick a specific one from your connected Qlik servers or reports, or turn on All tasks / All apps to watch every one at once (see Watch one or all).

3. Choose when it should fire: on success, on failure, or whenever the watched event finishes either way.

4. Optionally set a notification window to limit how often the same task or app can email you (see Notification window).

5. Pick the recipient group to notify, and give the alert a clear name.

6. Save. The alert runs automatically from then on - there’s nothing to schedule separately.

Watch one or all

When watching a Qlik task reload or a Qlik Cloud app reload, you can either pick a single task or app, or turn on All tasks / All apps to watch every one at once. An “all” alert fires for every reload, so a single alert can cover your whole environment - combine it with fire on failure to hear about any failure anywhere, without creating one alert per task.

Notification window

For reload alerts you can set a notification window (in minutes) to limit how often the same task or app emails you:

• Within the window, repeated reloads with the same result send at most one email.
• A change - a new failure, or a recovery after a failure - always emails you, even inside the window.
• Leave it at 0 to be emailed on every reload.

This is handy for tasks that reload frequently, or for an All tasks / All apps alert, so a burst of reloads doesn’t flood the recipients while still surfacing anything that actually changed.

Tip

Reload alerts fire the instant a reload finishes because of how each connection type notifies KPImailer: an on-premise server needs the UDP listener configured separately in Qlik Sense, while a Qlik Cloud tenant’s webhook is provisioned automatically the first time you connect it - see Setting up Qlik Cloud access.

Worked example

A nightly Qlik reload feeds the sales dashboard, and the data team wants to know immediately if it fails so they can fix it before the morning. They create an alert watching that reload task, set it to fire on failure, and point it at the Data Team recipient group. If the reload fails overnight, the group gets an email before anyone opens the dashboard.

Tip

Alerts and report send rules solve different problems: an alert notifies people about a Qlik event; a send rule decides whether a report sends at all. Use both together when a failed reload should both alert the data team and suppress a report that would otherwise show stale data.