---
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


---

# Running on-demand scans

# Running on-demand scans {#ariaid-title1}

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

You can initiate some scan types on-demand to run whenever they are required.

You can initiate the following scan types on-demand.
{#using-impact-scan-engine__table_jxp_zlk_hhc__entry__2}

| Scan type | Description |
|-|-|
| Application scans | Scan in-development applications to identify definition findings before publishing to the application repository. Application scans give insight into health scores, the number of findings, and the total impact of findings within your custom applications.  Hinweis: View application health scores in the Application Health dashboard by navigating to ALL \> Impact \> Platform Health \> Application Health. Health scores are calculated based on finding severity, count, and policy impact. |
| Limited definition scans  | Scan your instance against a single specified definition or definition suite. |
| Update set scans  | Scan open update sets for findings to get insights into what you are importing and exporting across your environments.  |
| Instance scans  | Scan your ServiceNow instance for findings. These scans return the findings and store them in the Opens Findings table.   Hinweis: Only users with the Scan Engine Admin role can initiate instance scans. |
[ ]

{#using-impact-scan-engine__table_jxp_zlk_hhc}

Scheduled instance scans can be executed immediately using the Execute Now action, but they cannot bypass their configured schedule settings. Real-time scans run automatically during record saves and cannot
be manually triggered.  
Hinweis:  
The Scan Engine integrates with certain development tools, such as App Engine Studio, ServiceNow Studio, and script editors. It scans business rules, script `includes`, UI scripts, client scripts, ACLs, record producers, and other script-containing records in real-time as they are saved.

Scans are initiated in different ways. They run using the Scan Engine properties you configured.

For more information, see [Configure Scan Engine properties](https://servicenow-prod.fluidtopics.net/dJMsPAzmxuEiFIbk9LPe9w "Configure the primary scanning capabilities and configuration options for scheduled, on-demand and real-time scans.") and [Configure definition properties](https://servicenow-prod.fluidtopics.net/qwv5jNRputWHcq1j3bkIOQ "You can configure additional capabilities and configuration options for the definition ruleset.").
**Zugehörige Konzepte**   

* [Full and delta instance scan initiation](https://servicenow-prod.fluidtopics.net/M5Wwgx2HsQ3nd7WJOT8bVg "The full and delta instance scan feature enables ServiceNow administrators and developers to initiate, monitor, and manage instance scans directly from the Scan Results list view.")  
**Zugehörige Informationen**   

* scan-engine-parallel-processing-task.html