---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Configure exception approval behavior

# Configure exception approval behavior {#ariaid-title1}

* Release version: Australia
* 
* Updated July 27, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Configure how exception reasons are enforced, approved, and re-evaluated when findings are detected using the ServiceNow
Scan Engine.

## Before you begin

When real-time enforcement is on, Act and Recommend level findings require an approved exception reason before the form can be saved. Suggest and Review level findings do not block form submission.

All instances must be registered in My SN Instances before configuring approval settings. See [Register your instance](https://servicenow-prod.fluidtopics.net/CW_9LTbn1YISzXh4d4sYSg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.") for details.

See [Understand scan results and findings](https://servicenow-prod.fluidtopics.net/JKkHFxhrSjWTuX8tUfjzrw "After a scan runs, you can monitor its progress in real-time, review the completed results, and then work with the findings to resolve issues in your instance.") for additional information on finding levels.

Role required: Scan Engine admin (sn_se.scan_engine_admin)

## Procedure

1. Navigate to ImpactPlatform HealthScan EngineAdministrationPropertiesException reasons.  
   Configuration options for Exception Reasons displays.
2. Set Enforce rejected exception reason validations to set enforcement behavior.  
   When enabled and an exception reason is rejected, the linked object becomes read-only until the finding is resolved or a new exception reason is submitted.  
   Important:  
   Enable this option for production instances.
3. Configure approval settings.  
   Important:  
   Before enabling approvals, ensure your instances are registered in My SN Instances with the exact instance name matching your instance subdomain. For example, use `testservicesdev` not `DEV`. If the instance name is incorrect, the Enable approvals in production checkbox will remain greyed out. See [Register your instance](https://servicenow-prod.fluidtopics.net/CW_9LTbn1YISzXh4d4sYSg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.") for details.
   1. Set Enable approvals in production.  
      Controls whether exceptions can be approved in the production instance, or only in the environment where they were raised.  
      Note:  
      This setting applies to production instances only. If set to false, exceptions raised in production must be approved in the originating development or non-production instance.
   2. Configure Approval groups.  
      Add the group or groups that will approve or reject exception reason requests and receive notifications when new requests are submitted.

      In the Approval group(s) field, select your lab approval
      group.
4. Set Exclude approved exception reasons from technical debt.  
   When enabled, findings with an approved exception reason are excluded from technical debt metrics. The finding remains in the system --- it is not deleted.  
   Note:  
   Enable this option.
5. Control re-evaluation behavior.
   1. Set Upon new finding found.  
      Determines how an existing approved exception reason is handled when the same issue is detected in a subsequent scan.{#configure-exception-reasons-scan-engine__entry__2}

      | Auto Accept Existing Reason | Re-approve Existing Reason |
      |-|-|
      | The existing approved reason carries forward automatically. No re-approval required. | The existing reason is suspended and must be re-reviewed before it takes effect again. |
      [ ]

   2. Set Upon line number change.  
      Determines how an approved exception reason is handled when the finding's line number changes in the code --- for example, after a refactor.
      {#configure-exception-reasons-scan-engine__entry__6}

      | Auto Accept Existing Reason (default) | Re-approve Existing Reason |
      |-|-|
      | The exception reason stays approved even if the line number shifts. Use when minor code movement is expected. | Any line number change requires re-review. Use when line position is meaningful to the exception context. |
      [ ]

6. Select Save.

*[\>]: and then