Inactive notifications got activated again after Utah upgradeDescriptionBelow are a few of the notifications that got activated again i.e active as true which were actually set as false before the version upgrade from San Diego to UTAH patch 1. 1. Comment left on incident2. Incident closed3. Incident resolved4. Incident was opened Release or EnvironmentUTAH Patch 1CauseThis is a known defect that is tracked via PRB1595586ResolutionFollow the below steps to review the other impacted notification records.Open the latest version upgrade record from the upgrade history table as below Sample URL # https://instancename.service-now.com/nav_to.do?uri=sys_upgrade_history.do?sys_id=870109231b022110e3ac1f87b04bcb3f Navigate to the changes applied section, review the updated notification record one by one by setting up a filter like the below by comparing it with the same notification record from one of your other instances which is still on the lower version, and then deactivate in the instance which was recently upgraded if it is not active in the other instance. Sample URL # https://instancename.service-now.com/sys_upgrade_history_log_list.do?sysparm_query=file_nameSTARTSWITHsysevent_email_action%5Edisposition%3D2%5Eupgrade_history%3D870109231b022110e3ac1f87b04bcb3f%5Ereplace_on_upgrade%3Dfalse&sysparm_view=