SLAs are not starting after Tokyo upgradeIssue Service Level Agreements (SLAs) are not starting after Tokyo upgrade.CauseOn the customer instances, there is a system property named "com.snc.sla.contract.tables" which has a value of "fsm_service_order,incident". This system property used to be part of the plugin "Service Level Management - Contract Management Integration [com.snc.sla.contract2]" but was deprecated in the Madrid release. This plugin had not been activated by the customer and on checking the system property it had been manually created by a user back in 2017. Without the plugin "com.snc.sla.contract.tables" being active this system property has no effect on SLA processing. ResolutionHowever, from Tokyo, this plugin is activated and installed by default. So SLA processing on the instance is now checking this system property and any table listed will now only evaluate SLA definitions that are linked to the Contract selected on the Incident. As the Contract field is not being used when logging Incidents this field is empty and so no SLA Definitions are evaluated. On modifying this system property (https://<instance_name>.service-now.com/nav_to.do?uri=sys_properties.do?sys_id=4c74b0474f247a008c8908111310c769) to remove the "incident" table and now SLAs are attaching as expected to Incidents. Recommendation: Delete system property "com.snc.sla.contract.tables". This will not change anything about SLA processing and will not impact any future use of processing SLAs by the selected Contract.