---
sourceDocument: Brazil Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/impact

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Sync exception reasons

# Sync exception reasons {#ariaid-title1}

Release version: Brazil  
Updated October 28, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure the Exception reason integration to automatically synchronize exception reasons between your non-production and production instances.

## Before you begin

My SN Instances registration and authentication must be complete before configuring this integration. Instance names must match the exact instance subdomain. For example, use `testservicesdev` not `DEV`. See [Register your instance](https://www.servicenow.com/docs/qVtcMVX4ueNM5WLtwJLobg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.").  
Important:  
Verify that instance names in the My SN Instances table match the exact instance subdomain before proceeding.

Role required: sn_se.scan_engine_admin

## Procedure

1. Navigate to AllImpactConfigurationScan Engine Properties.
2. Select the Exception Reason tab.
3. Configure the integration 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://www.servicenow.com/docs/qVtcMVX4ueNM5WLtwJLobg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.") for details.

   To require production approval before exception reasons take effect, select Enable approvals in production on each non-production instance, and specify one or more approval groups on production. Exception reasons will sync in a
   Requested state until approved or rejected.
{#syncing-exception-reasons__steps_xfk_1tv_djc}

## Result

Exception reasons created or updated on non-production instances are automatically synchronized to production. If approvals are enabled, the status syncs back to the instance where the exception was raised after a decision is made.

*[\>]: and then