Warning Notifications not Working

[KarthigaiMohan]

Hi , 

We have a seen a scenario where there was a table in the source a column was newly added with the length of the object name more than 32 charecters. This caused warnings in the logs , but then we did not get any error in the task. CDC task was running, but it had stopped capturing the changes from the source. Later we had identified it and had asked the source rename the column.  we already had got some clarification on this to how to allow object name more than 32 char. link below. 

Replicate - Oracle source: Long Object Names excee... - Qlik Community - 1961484

Question here is we would like to Monitor such Warnings , where the source changes stops to capture. we tried enabling the Warning Notification but we donot see the notification sent to email ( we do see error notifications sent to email, so smtp looks good). 

Screenshot of Config Attached. Please let us know how can we get the Warning notification enabled so that we can monitor from the windowslogs/email 

[Steve_Nguyen · Accepted solution]

you may want to look at QEM notification where :

Any warning:

No changes were captured in the last

[N]minutes(Requires Replicate May 2022 or later)

[Heinvandenheuvel]

This issue is supposed to be captured in a Development or QA deployment verification.

Error and Warning reporting are for dynamic, runtime events. This was a static, development time error. Fix it and move on.

>> This caused warnings in the logs , but then we did not get any error in the task.

I'm not sure I understand. 'Where' in the task, other than the log? Did the message not also appear on the UI - monitor  - Log messages. 

>> CDC task was running, but it had stopped capturing the changes from the source. 

I probably should try, but was the task 'dark green'? In an infinite retry loop? Was the offending table not suspended and other tables continued to replicate? Anyway, surely this was found on the first test in development and never made it to production. As such does not warrant a production time Email imho.

btw... Setup pictures are OK, but I personally find extracting the relevant chuncks of JSON describing settings more useful as that can be readily incorporated in a test. Pixels are less useful imho.

Hein.

At any rate, this should have