Suggest an Idea

[l9phan1]

Below are some screenshots and description on what happened.
Considering the following chain SAP ECC > SLT > EDH > QR > Snowflake, when a developer/support analyst removes a table from the SLT job (SAP ECC > SLT > EDH),
then SLT removes all objects that are depending on that table (e.g. triggers, permissions) on the target system (EDH).
Replicate didn’t recognize that its triggers were deleted and the web UI still shows that the task is running, so the team wasn’t aware that something is wrong with the task.
I am requesting that Qlik throw an error and STOP the task in this case instead of show the task status is Running.
This will help the people whom monitor the task aware of something wrong and working toward a resolution.

[Ola_Mayer]

we are looking at a solution and delivery time frame

[l9phan1]

Thank you Ola.

[Nulee_Massaro]

Notification available when no changes were captured in the last <n> minutes in May 2022 release. 

https://help.qlik.com/en-US/enterprise-manager/May2022/Content/EnterpriseManager/Main/Messages/task_...

[aplima]

@Nulee_Massaro I don't think the notification actually delivers what was asked in the feature request.

The notification should be helpful for high churn tables but will raise false positives for slow changing tables on the same task, moreover, it does not really relate with checking if triggers are there or not.

Our original request was for Qlik Replicate to identify tables that are missing triggers on the source HANA table and stop the task with an error.