Repeated Notification Provider warnings in logs related to com.glide.script.RhinoEcmaError: Cannot read property "actor" from undefined com.glide.script.RhinoEcmaErrorIssue Repeated Notification Provider warnings appear in the application node logs during Employee Center notification processing. The warnings include similarly structured errors with the following information about a field: com.glide.script.RhinoEcmaError: Cannot read property "actor" from undefined In this example the stack trace that is followed SysLog *** WARNING *** Evaluator: com.glide.script.RhinoEcmaError: Cannot convert null to an object. sys_script.00d7af5087f6c3102b4b77b5cebb352c.script : Line(9) column(0) 6: return; 7: } else { 8: ==> 9: var scToolsRetentionPolicy = grSCToolItem.getValue('retention_code').toString(); 10: if (current.getValue('u_retention_policy') != scToolsRetentionPolicy) { 11: current.setValue('u_retention_policy', scToolsRetentionPolicy); 12: current.setWorkflow(false); // skip re-triggering BRs Stack trace: at sys_script.00d7af5087f6c3102b4b77b5cebb352c.script:9 (executeRule) at sys_script.00d7af5087f6c3102b4b77b5cebb352c.script:16 The error is reported in the PortalProviderUtilSNC Business Rule when the sys_ids are traced back to the instance Facts This article addresses a scenario in which these warnings were associated with a failing custom Business Rule. The Notification Provider error alone does not confirm that the same customization issue is present on another instance. As an initial troubleshooting step (from KB3144344), review the update status of Notifications from Employee Center and the following related applications: Content Engagement for Employee Center Pro (sn_ex_sp_notifs) Employee Center Pro (sn_ce) Employee Center (sn_ex_sp) Employee Center Core (sn_hr_sp) Release N/A Cause A custom Business Rule attempted to call .toString() on a null value returned by getValue(). This generated an additional error in the application node logs: var retentionPolicy = sourceRecord.getValue('retention_code').toString(); When the field value was null, the conversion failed. The customization interfered with the normal execution of the out-of-box MetadataSearchApiHandler. Although the Notification Provider warning referenced PortalProviderUtilSNC, the identified issue was in the custom Business Rule. Resolution Identify the failing custom script Review the application node logs for errors occurring around the same time as the Notification Provider warnings. Look for the following message: sys_script.<business_rule_sys_id>.script : Line(9) column(0) Stack trace: at sys_script.<business_rule_sys_id>.script:9 (executeRule) Use the record identifier from your instance’s stack trace to locate the affected Business Rule. Record identifiers and line numbers vary by instance and customization. Review recent changes and version history of the identified business rule Inspect the failing line for operations that assume a field contains a value, such as calling .toString() without first handling a null value. Review the Business Rule’s available version history and compare the current script with a previously working version. Show XML can also be used to inspect the sys_updated_on value and help determine whether a recent update coincides with the start of the warnings. Restore the previously working customization The recommended remediation for this scenario is to revert the affected custom Business Rule to a known working version from before the issue began. Validate the change in a non-production environment before applying it to production. If the customization must be retained, review and correct its handling of null or empty values before redeploying it. Do not modify PortalProviderUtilSNC solely because it appears in the Notification Provider stack trace; investigate the underlying custom-script failure first. Validate the results Repeat the affected workflow and review the application node logs. Confirm that the custom Business Rule no longer produces the null-conversion error, the related Notification Provider warnings no longer recur, and MetadataSearchApiHandler executes as expected. If the warnings continue, investigate other errors associated with the same notification-processing activity rather than assuming that this customization was the only cause.