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

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Submit exceptions for the Scan Engine findings

# Submit exceptions for the Scan Engine findings {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

For Recommend level findings, developers can submit exception requests if they feel the issue should not be considered a finding.

## Vorbereitungen

Role required: Scan Engine Admin (sn_se.scan_engine_admin).

Generally, exceptions require approval from a system administrator. However, certain settings configured by a system administrator may determine if the exception is automatically approved or rejected.

## Prozedur

1. From the finding record, select Scan Engine Exceptions.  
   This displays all applicable script issues identified by the Scan Engine that also qualify for an exception.
2. Enter your reasoning for why an exception should be made for this finding in the Exception Reason field.
3. To have the exception reviewed by a system administrator, select Request Approval.  
   If enabled, the exception state is Requested. If not, the state is Not Yet Requested.
4. Select OK to file the exception request.  
   Once the exception request is saved, the applicable warning messages now show as blue and the file can be saved.

## Nächste Maßnahme

For more information on configuring exception properties, refer to [Configure exception reason properties](https://servicenow-prod.fluidtopics.net/2pxP7WKHt4pDQe~NZkP3vA "When real-time enforcement, enforce_real_time_validation is set to true, Recommend level findings require an approved exception reason before the form can be saved.").