topic Re: Qlik Notification Task Still sending Notifications after marking Inactive in Qlik Replicate

Qlik Notification Task Still sending Notifications after marking Inactive

jm32 — Mon, 18 Dec 2023 19:51:21 GMT

We had a notification on a task that would send an email based on a certain latency level being reached. We marked that notification as inactive and STILL receiving notifications. We then went in and removed the Email from the notification and still receiving emails. Why would we still be receiving these notifications?

Re: Qlik Notification Task Still sending Notifications after marking Inactive

lyka — Mon, 18 Dec 2023 20:02:18 GMT

Hello,
After making the change to make the notification inactive, did you start and resume the task? Any changes on the server configuration level requires a stop/resume for it to take effect

Thanks
Lyka

Re: Qlik Notification Task Still sending Notifications after marking Inactive

jm32 — Tue, 19 Dec 2023 17:09:03 GMT

We have over 50 tasks. We need to stop and resume every single one so that the server level notification gets inactived?

Re: Qlik Notification Task Still sending Notifications after marking Inactive

Alan_Wang — Tue, 19 Dec 2023 17:24:26 GMT

Hi @jm32

For the tasks included in the notification, yes it will need a stop and restart. Similar to how task settings need a task restart for the new settings to apply to them, it is the same for notifications.

If you continue to get notifications after a task restart, please open a support case so we can investigate.

Re: Qlik Notification Task Still sending Notifications after marking Inactive

Dana_Baldwin — Tue, 19 Dec 2023 20:59:05 GMT

Hi @jm32

You have the option of stopping the Replicate Server service which will stop all the running tasks for you. When you restart the service, all the tasks that were running will also resume.

The only risk is if you have a stop timeout on any of the tasks, where it cannot write the place where if left off to disk. This would be indicated in the repsrv.log file in the ..\data\logs directory on the server. It's also shown in the user interface, but since you're not viewing the individual task on screen in this use case you should check the log file.

If there was a stop timeout, the tasks with that condition will need to be started from a timestamp to ensure no changes are missed, taking into account any latency present at the time the tasks were stopped.

Basically, a task stop timeout happens when applying the last batch to the target and closing the source and target connections does not take place in a timely fashion.

I hope this helps!

Dana