Events process fails to create sys_email records on processing events for event-based notifications and the notification_engine.process eventsIssue Events process fails to create sys_email records on processing events for event-based notifications and the notification_engine.process events The sys_events table records exist and are processed but no emails are seen.Release As per the Problem this issue is resolved in New York Patch 9 Orlando Patch 4 ParisCauseA 'read' ACL was introduced in New York on the cmn_notif device table that allows a user to read only their cmn_notif_device. The instance has a user created with userID system. The events process runs as 'system' user and if the sys_user table contains a user with userID system, this user is impersonated to process the events. Because of the ACL this user is prevented from reading other users cmn_notif_device This results in no cmn_notif_device records retrieved for the intended recipients of the email. The system does not create an email if there are no recipients for the email. This can be confirmed by adding the following property and setting the value to 'true', we should see an email created with no recipients glide.email.notification.save_when_no_recipientsControls whether a notification-generated sys_mail record is saved even if there are no recipients. Used along with other notification recipient logging properties, this property enables investigating problems with notifications.Type: true | falseDefault value: trueResolutionCheck for a user named 'system' or sys_id is 'system' in the sys_user table Navigate to the sys_user tableSearch for a user named 'system' or sys_id is 'system'If a user is found, delete the user Restart the instance