Notification is not getting triggered

[Govardhan Ishta]

Hi ,

I have created a notification on sc_req_item table in ASFR Domain ( Parent Domain) then same notification has been reflected in all its child domains , Please find the Notification screen shots attached here .

When i was doing testing on child domain  i.e. by applying the conditions by changing the status from Delivered to Closed then notification is not getting triggered . Same notification has been created for Incident table here it is working as expected . i dont know why this is not working for sc_req_item .

Please help here to solve this issue .

[Mohith Devatte]

Hello,

I can see that your notification is being triggered by an event .

Di d you check if the event is getting fired ?

Navigate as below to check :

Event Log--> Search with your event name in name field -->sort by created z-a and check if the event is fired 

if not let us know we can debug

Please mark my answer correct if it helps you

[Govardhan Ishta]

Hi Mohith,

It's not getting triggered by an event , Please find new attached screen shot for your reference , and can you please help here to resolve this issue .

Thanks ,

[Govardhan Ishta]

@Mohith Devatte Hi Mohith can you please respond on this.

[Tudor]

Hello,

Is there any other notification that is getting triggered at the same time with a lower weight?

I see that the current one has 500 and this might be the case:

Weight

[Required] Set a numerical value for the notification priority relative to duplicate notifications. Notifications that have the same target table and recipients, or the same subject and body, are considered duplicates. When there are duplicate notifications, the system only sends the notification with the highest weight. All other notifications are moved from the Outbox to the Skipped mailbox. The default value 0 causes the system to always send the notification (assuming the conditions are met). For example, suppose that a service desk agent adds a comment to an incident and shortly thereafter closes it. By default, these actions trigger both the Incident commented and Incident Closed notifications. However, both notifications are from the Incident table and also notify the incident caller. The system only sends the notification with the highest weight, which in this case is the Incident Closed notification. Note: The SMTP Sender scheduled job determines how often to send email. By default, this job runs every minute.

Hope this helps!

Tudor