Exception reason integration
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
- 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
When Enable approvals in production is selected in Scan Engine Properties, the following workflow applies:
- A developer creates or updates an exception reason on the non-production instance.
- The exception reason is synced to production in a
Requestedstate. - An approval request is sent to the configured approval group(s).
- After the request is approved or rejected, the status syncs back to the instance where the exception was raised.
Prerequisites
-
My SN Instances registration is complete. See Register your instance.
-
Authentication is configured. See Configure the Basic authentication method or Configure the OAuth authentication method development instance.
-
Role required:
sn_se.scan_engine_admin. -
Sync exception reasons
Configure the Exception reason integration to automatically synchronize exception reasons between your non-production and production instances.
Parent Topic:Scan Engine integrations
--- title: Exception reason integration description: You can synchronize exception reasons from non-production to Production instances after a record is created or updated. locale: en-US canonical_url: https://www.servicenow.com/docs/r/impact/exception-reason-integration.html release: brazil topic_type: concept last_updated: "2026-10-27" reading_time_minutes: 1 breadcrumb: [Scan Engine integrations, Activate Scan Engine and review settings, Configuring Impact, Impact] --- # Exception reason integration 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 - 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 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. ## Prerequisites - My SN Instances registration is complete. See [Register your instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/impact/register-your-instance.md). - Authentication is configured. See [Configure the Basic authentication method](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/impact/configure-basic-auth-method.md) or [Configure the OAuth authentication method development instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/impact/configure-oauth-auth-method.md). - Role required: `sn_se.scan_engine_admin`. - **[Sync exception reasons](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/impact/syncing-exception-reasons.md)** Configure the Exception reason integration to automatically synchronize exception reasons between your non-production and production instances. **Parent Topic:**[Scan Engine integrations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/impact/instance-integration-scan-engine.md)
| title | Exception reason integration |
| description | You can synchronize exception reasons from non-production to Production instances after a record is created or updated. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/impact/exception-reason-integration.html |
| release | brazil |
| topic_type | concept |
| last_updated | 2026-10-27 |
| reading_time_minutes | 1 |
| breadcrumb | Scan Engine integrationsActivate Scan Engine and review settingsConfiguring ImpactImpact |