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


---

# Sync exception reasons

# Sync exception reasons {#ariaid-title1}

* Release version: Australia
* 
* Updated July 27, 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://servicenow-prod.fluidtopics.net/CW_9LTbn1YISzXh4d4sYSg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.").

Role required: sn_se.scan_engine_admin
Figure 1. My SN Instances table showing correct instance name format

## Procedure

1. Navigate to ALLImpactConfigurationScan Engine Properties.
2. Select the Exception reason properties 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://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.

   To require production approval before exception reasons take effect, select Enable approvals in production and specify one or more Approval Groups. 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 developer instance after a decision is made.

*[\>]: and then