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


---

# Exception reason integration

# Exception reason integration {#ariaid-title1}

* Release version: Australia
* 
* Updated May 5, 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 once 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.

## 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. Once approved or rejected, the status syncs back to the developer instance.
{#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://servicenow-prod.fluidtopics.net/CW_9LTbn1YISzXh4d4sYSg "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://servicenow-prod.fluidtopics.net/cuVzGTUp4EYPFdAvW75jrw "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://servicenow-prod.fluidtopics.net/1yaYVDnxfcmFLl6Jpf0k0A "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://servicenow-prod.fluidtopics.net/OJ2Ur9zMmyqQlFi2pKSjtw)**   
  Configure the Exception reason integration to automatically synchronize exception reasons between your non-production and production instances.