notification is not triggered when the event is triggered by the scheduled job

[Keshava Reddy1]

I have created a scheduled job , event and notification in a domain separated instance. Here when the job is run the event is triggered and i can find the events in event log but the notification is not sent.

I have done the same process by creating notification, event and scheduled job in the global domain then it worked well.

Only problem is I am not able to get the notification when i use event based triggering of notification in domains other than global.

Can I get some help here because it is very urgent !!!!!!

[Community Alums]

Hi @Keshava Reddy ,

Please check if the Manager to whom you're sending is having an email id present on the user record, verify the user you have chosen has a manager or if you're using Users/ Groups in field on the Notification, then check that the user for whom you're doing it is having a manager updated in his user record or not.

do you have recipients in your notification set to Parm1?

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Keshava Reddy1]

yes there is a recipient set to parm1.

Here the problem is not with the notification. it is with the domain

if i use global domain it is sending a notification when the event is triggered but if i use other domain then it is not sending a notification

[Amy Lind3]

I know this is a bit old, but I wanted to throw in my findings as I was working to resolve a similar issue and this post brought me to this solution. 

I found that the inactivity event MUST be created in the global scope.  This is because when created within another scope, the event registration will force the Event name prefix.  Since the Event MUST be <<table_name>>.inactivity, this is impossible. 

Ex. For Security Incident Response, the Event name in the SIR scope was set to sn_si.task.inactivity.  It would not trigger the notification because the table name is sn_si_task.  I created sn_si_task.inactivity in the global scope and it worked!