---
sourceDocument: Brazil Service Exchange
sourceDocumentLink: https://www.servicenow.com/docs/r/service-exchange

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Service Exchange

ft:clusterId :

    - sebrdg

bundleId :

    - sebrdg

workflow :

    - Customer and Industry


---

# Automatic mitigations for known errors

# Automatic mitigations for known errors {#ariaid-title1}

Release version: Brazil  
Updated October 1, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Known errors with the Tier field set to Automatic are fixed without admin action when a Service Exchange connection goes down. Each fix changes specific records on your instance.
{#se-auto-mitigation-known-errors__table_auto_kecs__entry__4}

| Known error | Detects | Fix | If the fix fails |
|-|-|-|-|
| Inactive capture definitions | One or more Service Exchange capture definitions are inactive. | Activates the inactive capture definitions. | If a required capture definition is missing, the fix fails and the issue stays open. |
| Elevated privilege on RPS roles | Elevated privilege is turned on for one or more RPS roles. | Turns off elevated privilege on the RPS roles. Note: This fix changes role configuration without admin approval. | The issue stays open. |
| Inactive integration user | The integration user for the connection is inactive. | Reactivates the integration user. Note: This fix reactivates a user account without admin approval. | The issue stays open. |
| Integration user name doesn't start with sb_user | The user name of the integration user for the connection doesn't start with `sb_user`. | Renames the integration user so that the user name starts with `sb_user`. Note: This fix changes a user account without admin approval. | The issue stays open. |
[Table 1. Known errors fixed automatically]

{#se-auto-mitigation-known-errors__table_auto_kecs}

Every fix is recorded in the work notes of the related issue. For details on when fixes run, see [Automatic mitigation for connection issues](https://www.servicenow.com/docs/VulTJsd83eGVIUlsKMaCRw "Automatic mitigation detects known connection errors and fixes them without administrator action when a Service Exchange connection goes down. You review the results in issue work notes and act when a fix fails.").
**Related concepts**   

* [Automatic mitigation for connection issues](https://www.servicenow.com/docs/VulTJsd83eGVIUlsKMaCRw "Automatic mitigation detects known connection errors and fixes them without administrator action when a Service Exchange connection goes down. You review the results in issue work notes and act when a fix fails.")  
**Related reference**   

* [Known error code form](https://www.servicenow.com/docs/Ux7ybcZNSXVlmMxd0Wh_oQ "The known error code form defines a known Service Exchange error and controls whether the system fixes it automatically when a connection goes down.")
* [List of scan checks](https://www.servicenow.com/docs/TAqOlqTSQlm0EaV8~rDWdA "Multiple scan checks are available in Service Exchange to help you identify issues and system inconsistencies, enabling you to maintain system health and reduce downtime.")