Issue Statement: Scan engine Application not allowing to commit update set (backed up update set) in non-prod post cloning (prod->dev) ,development got stopped partially.
Description: In our Production instance , Scan Engine app was deployed for Instance scan.
Once production got cloned to Dev instance (non-prod) , while developers are trying to committing their update set (backed up update set), it is throwing error.
After it analysis developer has found out that following BR was causing the issue .
Again, we can not deactivated the BR (even after as a scan engine Admin) as it is protected by ServiceNow Protected policy which means only ServiceNow support can help to deactivate it.
Note: The Scan Engine Application is a ServiceNow application designed to automate recommended practice enforcement, manage technical debt, and optimize workflows across ServiceNow environments. It enables administrators and developers to proactively identify, remediate, and track issues through real‑time, on‑demand, and scheduled scans, ensuring continuous improvement in platform health and compliance. Integrated directly into the development lifecycle, it provides real‑time checks within App Engine Studio and script editors to prevent non‑compliant changes before they reach production, while offering intelligent fix suggestions to accelerate resolution.
How to Fix the issue: It can be fixed it following way,
1. If Scan Engine is not required in your non-prod, uninstall it.
Use the "Uninstall" related link on the following page:
https://<your instance name>.service-now.com/sys_store_app.do?sys_id=6f0f9bacfff12210a117ffffffffff78&sysparm_view=
** you will hit the URL with your Scan engine sys_id in sys_store_app table.
2. If you need the Scan engine app in non-prod, Raise a case to Servicenow vendor, they will disable it . once done, you can repair the plugin.
As per ServiceNow- The ideal solution here is
- to get started properly on all instances with Instance Scan (Impact): https://www.servicenow.com/docs/r/impact/impact-landing-page.html
However, you can make that decision according to your business requirements. All you need to do to reactivate that business rule is to "Repair" (related link) on the application page. - You can't exclude individual applications from cloning. Please proceed to fix forward / prepare for applications on source instance to push to target post clone.
