---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Refresh event rules

# Refresh event rules {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Manually update event rules to reflect current event information because once an
event rule is created, the Event Additional info and
Event Raw info fields are not automatically updated.

## Before you begin

Role required: evt_mgmt_admin

## About this task

Note:  
Use [Ignore automation](https://www.servicenow.com/docs/2vGPmqiB_MmLcy877la8hg "Ignore automation streamlines the process of disregarding irrelevant or false-positive alerts from monitoring systems, efficiently managing alert fatigue by filtering out unnecessary notifications. As a result, teams can prioritize and resolve critical issues more effectively.") and [Enrich automation](https://www.servicenow.com/docs/sxzwlcQ2n4ew7eLBl6ngzw "Alert enrichment involves transforming raw events from monitoring tools into a standard format, aiding automated grouping and response. This includes extracting fields from lengthy alert payloads or composing them into a standardized format. Additionally, you can create tags, which are metadata added to alerts for easier filtering and grouping.") in Service Operations Workspace, the updated way to automatically filter out irrelevant alerts, or to transform and standardize alert data for better response.

## Procedure

1. Navigate to AllEvent ManagementAll Events.
2. Select the event.
3. Select Refresh Event Rule.
4. Select the event rules to refresh.
5. Select Refresh Selected.  
   If you selected multiple event rules, then the last selected item in the list
   opens in the Event Rule Designer.  
   Note:  
   If the current event rule regex expressions do not match the selected event after the refresh, the update fails and an error message appears specifying the problematic fields. This safeguard ensures that your previously defined event rule regex expressions are not broken due to the refresh.

*[\>]: and then