---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Violation Logs

# Violation Logs {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The Runtime Policy Violation Log records network, record, and scripting violations encountered while exercising application functions, giving you a consolidated view of cross-origin or out-of-scope access attempts. The ARL
Violation Log records violations of event handlers, scheduled jobs, and API and UI transactions.

## Runtime Policy Violation Log

When Application Runtime Policy (ARP) is enabled in Tracking or Enforcing mode, the first instance of every
network, record, and scripting policy violation is recorded in the Runtime Policy Violation Log. You can review the log by navigating to AllSystem PolicyApplication Runtime PolicyRuntime Policy Violation Log. If access attempts that you want to allow are blocked while developing an application, you can use the log to find the policy record that needs to be reviewed and approved.

## ARL Violation Log

After the application is installed, platform resource usage violations are recorded at runtime. The ARL Violation Log includes violation records related to API and UI transactions, event handlers, and scheduled jobs. Administrators can review the log by navigating to AllSystem PolicyApplication Runtime PolicyARL Violation Log to determine whether to manually create policies on their instance for any violations.

*[\>]: and then