---
sourceDocument: Brazil ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# System Events

# System Events {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of System Events

System events in ServiceNow are special records that log when specific conditions occur and trigger actions in response.
These events are generated by business rules that monitor system conditions and insert event records into theEvent \[sysevent\]table, also known as the event log or event queue.
Show full answer Show less  
Events enable automated responses such as running scripts, sending notifications, or triggering workflows, helping streamline and automate system behaviors based on record changes.

## How Events Are Generated and Processed

* Business rules use conditional logic to determine when an event should be added to the event queue.
* For example, events like **incident.commented** , **incident.inserted** , and **incident.updated** are generated when comments are added, incidents created, or incidents updated.
* The **GlideSystem eventQueue** method is used to insert event records, which include key details such as:

| Field | Description |
|-|-|
| Name | Unique identifier of the event, usually combining record type and triggering action |
| Parm1 and Parm2 | Event-specific parameters to pass record information (e.g., Sys ID or field values) |
| Table | The table to which the event applies |
| Instance | Sys ID of the affected record |

Scheduled jobs read the event queue and forward events to appropriate handlers that execute actions such as running scripts, sending notifications, triggering workflow activities, or monitoring inactivity.

## Customization and Monitoring

* ServiceNow provides a broad set of baseline events, but customers can create custom events tailored to specific record changes or business needs.
* The **System Events and Jobs Dashboard** allows monitoring of event processing and scheduled jobs to ensure system operations are running smoothly.

## Event Processing During Platform Upgrades

Customers can control event processing during platform upgrades with system properties:

* **glide.eventprocessor.alleventsupgradesafe**: When set to true, all events are processed during upgrades (default is false).
* **glide.eventprocessor.upgradesafeevents** : When **alleventsupgradesafe** is false, this property lists specific events to process during upgrades.

This configuration helps maintain system stability by selectively processing essential events during upgrades.  
Events are special records that the system uses to log when certain conditions occur and to take some kind of action in response to the conditions.

The system uses business rules to monitor for system conditions and to generate event
records in the Event \[sysevent\] table, which is also known as the event log or event
queue.

Event-generating business rules typically use this script logic:

If \[some condition is true for the current record\], then \[add a specific event to the
queue\].  
For example, here are some of the conditions in the incident event business rule:

* If a user adds a comment to an incident record, add an incident.commented event.
* If a user adds an incident record, add an incident.inserted event.
* If a user updates an incident record, add an incident.updated event.
{#events__ul_xnm_jwg_vw}  
Event-generating business rules use the GlideSystem eventQueue method to insert event records, which typically contain this information:{#events__table_fjs_st1_vw__entry__2}

| Field | Description |
|-|-|
| Name | Unique name of event. Baseline event names include the record affected and the triggering action, such as incident.commented. |
| Parm1 | Event-specific parameter the system uses to pass record information to other parts of the system, such as a record Sys ID or a field value. |
| Parm2 | Event-specific parameter the system uses to pass record information to other parts of the system, such as a record Sys ID or a field value. |
| Table | Table to which the event applies. This is the same table on which the business rule ran. |
| Instance | Sys ID of the record to which this event applies. |
[Table 1. Event fields]

{#events__table_fjs_st1_vw}  
Scheduled jobs periodically read the event queue and forward them to the appropriate handler for processing. The handler uses information from event records to take some kind of action such as:

* Run a script action
* Send a notification
* Trigger a workflow activity
* Trigger an inactivity monitor
{#events__ul_vph_sq1_vw}

By default, the system provides events covering a broad view of application activity. If
existing events do not meet your needs, you can create your own events to watch for
specific changes to records.

For developer training, see [Scheduled Script Executions and Events Objectives](https://developer.servicenow.com/dev.do#!/learn/courses/xanadu/app_store_learnv2_automatingapps_xanadu_automating_application_logic/app_store_learnv2_automatingapps_xanadu_scheduled_script_executions_and_events/app_store_learnv2_automatingapps_xanadu_scheduled_script_executions_and_events_objectives)
on the ServiceNow®
Developer Site.

Use the [System Events and Jobs Dashboard](https://www.servicenow.com/docs/dBZo9gcclbK5DNMRyRTfKw "Use the System Events and Jobs Dashboard module to monitor the system event processing system and monitor the scheduled jobs processing system in the Scheduled Jobs dashboard tab.") to monitor the system event processing system and the scheduled jobs processing system.

## Event processing during platform upgrade {#events__section_t45_dqx_ktb}

Determine which events are to be processed during a platform upgrade by configuring the
following properties:

* glide.event_processor.all_events_upgrade_safe: Set to true to process all events during platform upgrade. Default = false.
* glide.event_processor.upgrade_safe_events: Configure a comma-separated list of event names to indicate that only specified events are processed. Default = \<empty\>.

  This property is relevant only when
  glide.event_processor.all_events_upgrade_safe = false.
{#events__ul_t2g_gqx_ktb}