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


---

# Rollback context properties

# Rollback context properties {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Rollback context properties

Rollback context properties in ServiceNow control the retention period of rollback context records, which store significant data needed to revert various changes such as app installs, upgrades, and data deletions.
By default, rollback contexts are deleted after 10 days to manage data size, but this retention period can be customized.
Show full answer Show less  
The **Clean Expired Rollback Contexts** scheduled job runs daily to remove expired records from the `sysrollbackcontext` table. Customers can extend retention by adding system properties that specify how many days rollback contexts should be kept for different rollback types.

## Key Features

* **Customizable expiration periods:** You can define the number of days rollback contexts are retained by adding properties in the `sysproperties` table. Each property corresponds to a specific rollback type.
* **Type-based property mapping:** The property name must match the `Type` column in the rollback context table to apply the correct expiration period.
* **Support for various rollback types:** Properties exist for app installs, batch app installs, demo data, delete operations, workflow validations, CMDB Integration Studio changes, plugin activations, anonymization jobs, background scripts, test executions, upgrades, and "other" types.
* **Extended retention for stuck rollback contexts:** A special property `glide.rollback.stuckexpirationdays` allows retaining stuck rollback contexts beyond their normal expiration by a configurable number of days (default 30).

## Practical Use for ServiceNow Customers

If you require rollback contexts to be available longer than the default retention period for auditing, troubleshooting, or compliance reasons, you can extend these periods by adding or updating the corresponding system properties. For example:

* Extend app install rollback retention beyond 15 days using `glide.rollback.expirationdaysappinstall`.
* Adjust retention periods for plugin activations or upgrades when longer rollback windows are necessary.
* Increase retention for rollback contexts related to data deletions, workflow validations, or anonymization jobs to ensure adequate recovery time.

By tailoring these settings, you maintain control over rollback data lifecycle, balancing storage concerns against your rollback and recovery needs.  
Change the default expiration period for different types of rollback context records.
Because rollback contexts contain a significant amount of data, they're deleted after 10 days by default. The Clean Expired Rollback Contexts scheduled job runs daily to delete expired records in the Rollback Context
\[sys_rollback_context\] table. If you need to retain a rollback context for more than 10 days, you can do so by adding a system property.

To add a system property, navigate to the System Properties \[sys_properties\] table and add a property for the type of rollback context record that you want to preserve. You can determine which property to add for a given rollback
context by matching the property name to the Type column on the Rollback Context \[sys_rollback_context\] table.  
{#rollback-context-properties__table_okp_mc3_l1c__entry__2}

| Property | Description |
|-|-|
| The number of days to retain the rollback context for an app install `glide.rollback.expiration_days_app_install` | By default, you have 15 days to roll back an application installed from the ServiceNow® Store before the rollback context expires. You can extend the expiration period by updating this property. * Type: integer * Default value: 15 {#rollback-context-properties__ul_qfv_ysm_l1c} |
| The number of days to retain the rollback context for a batch app install `glide.rollback.expiration_days_batch_app_install` | By default, you have 10 days to roll back apps installed using the Batch Installation feature before the rollback context expires. You can change the expiration period by adding this property and setting a new value. * Type: integer * Default value: 10 {#rollback-context-properties__ul_x1x_zsm_l1c} |
| The number of days to retain the rollback context for demo data `glide.rollback.expiration_clean_demo_data` | By default, you have 10 days to roll back before the rollback context expires. You can change the expiration period by adding this property and setting a new value. * Type: integer * Default value: 10 {#rollback-context-properties__ul_rwr_g4c_h2c} |
| The number of days to retain the rollback context for recorded delete operations `glide.rollback.expiration_days_delete` | By default, you have 10 days after a delete operation completes to roll back before the rollback context expires. You can change the expiration period by adding this property and setting a new value. * Type: integer * Default value: 10 {#rollback-context-properties__ul_fqy_wcc_h2c} |
| The number of days to retain the rollback context created for validating Workflow Studio flow execution before and after an upgrade `glide.rollback.expiration_days_flow` | By default, you have 10 days to roll back before the rollback context expires. You can change the expiration period by adding this property and setting a new value. * Type: integer * Default value: 10 {#rollback-context-properties__ul_lsz_qkc_h2c} |
| The number of days to retain the rollback context for IRE changes recorded from CMDB Integration Studio. `glide.rollback.expiration_days_inst_preview` | By default, you have 10 days after IRE changes are recorded from CMDB Integration Studio to roll back before the rollback context expires. You can change the expiration period by adding this property and setting a new value. * Type: integer * Default value: 10 {#rollback-context-properties__ul_vrt_n3c_h2c} |
| The number of days to retain rollback contexts in which the Type is set to Other. `glide.rollback.expiration_days_other` | By default, you have 10 days to roll back before the rollback context expires. You can change the expiration period by adding this property and setting a new value. * Type: integer * Default value: 10 {#rollback-context-properties__ul_klt_w4c_h2c} |
| The number of days to retain the rollback context for a plugin activation `glide.rollback.expiration_days_plugin` | By default, you have 15 days to roll back plugins activated in Application Manager before the rollback context expires. You can extend the expiration period by updating this property. * Type: integer * Default value: 15 {#rollback-context-properties__ul_htv_4hc_h2c} |
| The number of days to retain the rollback context for an anonymization job. `glide.rollback.expiration_days_redact` | By default, you have 10 days after data is redacted by a Data anonymization job to roll back before the rollback context expires. You can change the expiration period by adding this property and setting a new value. * Type: integer * Default value: 10 {#rollback-context-properties__ul_hbm_3jc_h2c} |
| The number of days to retain the rollback context for a background script execution `glide.rollback.expiration_days_scripts_bg` | By default, you have 10 days to roll back script execution before the rollback context expires. The rollback context tracks all INSERT, DELETE, and UPDATE statements executed by the script and recovers the data by undoing the SQL statements. You can extend the expiration period by updating this property. * Type: integer * Default value: 10 {#rollback-context-properties__ul_i2c_gxy_rbc} |
| The number of days to retain the rollback context for changes recorded during test executions `glide.rollback.expiration_days_test_execution` | By default, you have 10 days after test execution to roll back before the rollback context expires. You can change the expiration period by adding this property and setting a new value. * Type: integer * Default value: 10 {#rollback-context-properties__ul_f4l_d3c_h2c} |
| The number of days to retain the rollback context for an upgrade `glide.rollback.expiration_days_upgrade` | By default, you have 10 days after the latest upgrade to roll back the upgrade before the rollback context expires. You can change the expiration period by adding this property and setting a new value. * Type: integer * Default value: 10 {#rollback-context-properties__ul_xb2_rhc_h2c} |
| The number of additional days to retain rollback contexts that are stuck, beyond the normal expiration period. `glide.rollback.stuck_expiration_days` | By default, rollback contexts that are stuck are retained for an additional 30 days beyond the normal expiration period. You can change this retention period by adding this property and setting a new value. The total retention period for stuck rollback contexts is calculated by adding the value of `glide.rollback.stuck_expiration_days` to the normal expiration period defined by `glide.rollback.expiration_days_delete`. By default, the normal expiration period is 10 days, so if `glide.rollback.stuck_expiration_days` is set to 30, stuck rollback contexts will be retained for a total of 40 days (10 + 30). The `glide.rollback.stuck_expiration_days` property is valid for all rollback types, not just for delete. * Type: integer * Default value: 30 {#rollback-context-properties__ul_sxb_1tb_xgc} |
[Table 1. Rollback context properties]

{#rollback-context-properties__table_okp_mc3_l1c}

