How to fix email notifications not creating records in non-global domains or scopesIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When you create an email notification in a non-global domain or scope that triggers on a specific event, the email record may not be created even when all conditions are met and recipients are correctly configured. In the Events Log, the event is visible that should trigger the notification, but the Table field is empty. There is also a notification_engine.process event with a Parm1 sys_id that matches the notification sys_id. This confirms the notification conditions are met. When the notification engine process event is finished, the node log shows processing activity similar to the following: 2020-04-13 10:40:04 (290) worker.5 worker.5 txid=6030b957db84 *** Start Background transaction - system, user: system2020-04-13 10:40:04 (296) worker.5 worker.5 txid=6030b957db84 Starting: events process 1.999460131b0100103fc78596dc4bcb41, Trigger Type: Interval, Priority: 25, Upgrade Safe: true, Repeat: 10 Seconds2020-04-13 10:40:04 (296) worker.5 worker.5 txid=6030b957db84 Name: events process 12020-04-13 10:40:04 (427) worker.5 worker.5 txid=6030b957db84 EMAIL.e030f957db8450106f1e74dfaa961965: Notification 'Test Notification' (6b1295dbdb0450106f1e74dfaa9619d0) included recipients via the notification's "Users" field: 'John Doe' (16139f900a0a3ce00120d33ac8629853)2020-04-13 10:40:04 (439) worker.5 worker.5 txid=6030b957db84 Completed: events process 1 in 0:00:00.139, next occurrence is 04-13-2020 13:40:06 Despite the indication that an email was created, no sys_email record appears. For example, the event notification includes the following code: gs.eventQueue("my_event", current, 'Text for Parm1' , 'Text for Parm2'); In this case, the current variable does not point to any record object, which results in an empty Table field in the event. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All supported releases Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Unless you specify an associated record object when creating the event, an event won't create an email record in a non-global domain or scope that triggers from an event. Without a record object, the system runs in the global domain or scope. Since the notification exists in a different domain or scope, the notification doesn't trigger. If your notification is in the global domain and scope, you don't need to specify a record object because the system already runs in the global domain or scope. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } You can resolve the issue in two ways: 1. Use event creation to pass the domain or scope record to the notification Modify your event creation to include a record object in the second parameter of eventQueue(). This places the system into the same domain or scope as the notification. Change your event creation from: gs.eventQueue("my_event", current, 'Text for Parm1', 'Text for Parm2'); To: var myGlideRecord = new GlideRecord('sys_user');myGlideRecord.addQuery('sys_id','16139f900a0a3ce00120d33ac8629853');myGlideRecord.query();if(myGlideRecord.next()){gs.eventQueue("my_event",myGlideRecord, 'Text for Parm1' , 'Text for Parm2');} This associates the event with a record in the sys_user table. The specific record used isn't important. When you view the event in the event log, the Table field is now populated. 2. Place the notification in the global domain and scope Move the notification to the global domain and global scope. In this configuration, the event creation does not need to reference a record object since the system runs in the global domain or scope, which matches the notification domain or scope.