Rollback context properties

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

**Parent Topic:**[Roll back and delete recovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-administration/table-administration-and-data-management/rollback-delete-recovery.md)

title	Rollback context properties
description	Change the default expiration period for different types of rollback context records.
locale	en-US
canonical_url	https://www.servicenow.com/docs/r/platform-administration/table-administration-and-data-management/rollback-context-properties.html
release	brazil
product	Table Administration and Data Management
classification	table-administration-and-data-management
topic_type	reference
last_updated	2026-09-10
reading_time_minutes	4
breadcrumb	Roll back and delete recoveryTables and dataConfigure core featuresAdminister the ServiceNow AI Platform