sn_itam_health_chk plugin is taking long during Yokohama to Zurich upgrade ~ 33 MinutesDescriptionUpgraded instance - testingnikecdt1 from Yokohama Patch 3 to Zurich (glide-05-14-2025_1730.zip) and observed that sn_itam_health_chk plugin is taking long during Yokohama to Zurich upgrade ~ 33 MinutesPlease find attached the screenshot.Steps to Reproduce Upgraded instance - testingnikecdt1 from Yokohama Patch 3 to Zurich (glide-05-14-2025_1730.zip) and observed that sn_itam_health_chk plugin is taking long during Yokohama to Zurich upgrade ~ 33 MinutesPlease find attached the screenshot.WorkaroundThe upgrade time is directly proportional to the number of scan_findings present in the instance during upgrade from below checks.SAM - Stale VMs or Hosts consuming LicenseSaas - M365 - Installation checkSo during upgrade when we deleted those above two checks, Because of cascade rule findings are also getting deleted which is taking time.Customer should ideally have a table cleaner rule defined in instance scan application so that all the stale entries gets cleared out before upgrade. This feature is owned by instance scan team.Also customer who upgraded to ZP1 already wont face the issue again while upgrading to newer patches.Related Problem: PRB1893349