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


---

# Exception reason integration

# Exception reason integration {#ariaid-title1}

Release version: Brazil  
Updated October 27, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
You can synchronize exception reasons from non-production to Production instances after a record is created or updated.

When a developer creates or updates an exception reason on a non-production instance, the integration automatically propagates that change to the production instance. If production approvals are enabled, the exception reason
enters a Requested state and triggers an approval workflow before taking effect.

## Where to configure {#exception-reason-integration__section_where_to_configure}

* On each non-production instance where you want exceptions approved in production, select Enable approvals in production.
* On production, specify the approval group in the Approval group(s) field on the Exception Reason tab of Scan Engine Properties, in the Exception Behaviour section. That group is notified when a new exception is raised.

## Approval workflow {#exception-reason-integration__section_fzx_3sv_djc}

When Enable approvals in production is selected in Scan Engine Properties, the following workflow applies:

1. A developer creates or updates an exception reason on the non-production instance.
2. The exception reason is synced to production in a Requested state.
3. An approval request is sent to the configured approval group(s).
4. After the request is approved or rejected, the status syncs back to the instance where the exception was raised.
{#exception-reason-integration__ol_gzx_3sv_djc}

## Prerequisites {#exception-reason-integration__section_hwj_msv_djc}

* My SN Instances registration is complete. 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.").
* Authentication is configured. See [Configure the Basic authentication method](https://www.servicenow.com/docs/sqSEawQaR6_jbGjrlIhFCQ "Confirm an integration user, create a Basic authentication record, then connect your instances using basic authentication. Basic authentication is supported but OAuth is recommended for production environments.") or [Configure the OAuth authentication method development instance](https://www.servicenow.com/docs/JMYCW35QMol3B5RjYlAheQ "Set up OAuth authentication for instance-to-instance Scan Engine integrations using several stages, an integration user account, an OAuth2 configuration record, and provider and client application registries.").
* Role required: `sn_se.scan_engine_admin`.
{#exception-reason-integration__ul_iwj_msv_djc}
* **[Sync exception reasons](https://www.servicenow.com/docs/X_XYYxmbInC6oT_Su_LuDg)**   
  Configure the Exception reason integration to automatically synchronize exception reasons between your non-production and production instances.