Rollback context properties
Summarize
Summary of Rollback context properties
Rollback context properties in ServiceNow determine how long rollback context records are retained before automatic deletion. Rollback contexts store significant amounts of data related to various rollback events and are deleted by default after 10 days through the dailyClean Expired Rollback Contextsscheduled job. Customers can extend the retention period for different rollback context types by adding or updating specific system properties.
Show less
Configuring Rollback Context Retention
To retain rollback contexts longer than the default period, navigate to the System Properties [sysproperties] table and add or update the appropriate property corresponding to the rollback context type. Match the property name with the Type column in the Rollback Context [sysrollbackcontext] table to identify which property to modify. Each property defines the number of days to retain rollback data before it expires and is deleted.
Key Properties and Their Defaults
- glide.rollback.expirationdaysappinstall: Retains rollback data for app installations from the ServiceNow Store. Default is 15 days.
- glide.rollback.expirationdaysbatchappinstall: Controls retention for batch app installs. Default is 10 days.
- glide.rollback.expirationcleandemodata: Retains rollback for demo data. Default is 10 days.
- glide.rollback.expirationdaysdelete: Retains rollback data for recorded delete operations. Default is 10 days.
- glide.rollback.expirationdaysflow: Retains rollback context for Workflow Studio flow execution validations. Default is 10 days.
- glide.rollback.expirationdaysinstpreview: Retains rollback for IRE changes from CMDB Integration Studio. Default is 10 days.
- glide.rollback.expirationdaysother: Retains rollback contexts of type "Other". Default is 10 days.
- glide.rollback.expirationdaysplugin: Retains rollback for plugin activations in Application Manager. Default is 15 days.
- glide.rollback.expirationdaysredact: Retains rollback data for anonymization jobs. Default is 10 days.
- glide.rollback.expirationdaysscriptsbg: Retains rollback context for background script executions that track SQL changes. Default is 10 days.
- glide.rollback.expirationdaystestexecution: Retains rollback for changes recorded during test executions. Default is 10 days.
- glide.rollback.expirationdaysupgrade: Retains rollback data for upgrades. Default is 10 days.
Practical Impact for ServiceNow Customers
By configuring these properties, ServiceNow customers can control how long rollback contexts remain available, allowing more time to undo changes related to application installs, plugin activations, upgrades, data anonymization, and other system operations. This flexibility helps ensure data recovery options align with organizational policies and operational requirements, while managing storage concerns associated with large rollback data sets.
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
|
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.
|
The number of days to retain the rollback context for a 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.
|
|
The number of days to retain the rollback context for 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.
|
|
The number of days to retain the rollback context for recorded delete operations
|
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.
|
|
The number of days to retain the rollback context created for validating Workflow Studio flow execution before and after an upgrade
|
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.
|
|
The number of days to retain the rollback context for IRE changes recorded from CMDB Integration Studio.
|
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.
|
|
The number of days to retain rollback contexts in which the Type is set to 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.
|
|
The number of days to retain the rollback context for a plugin activation
|
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.
|
|
The number of days to retain the rollback context for an anonymization job.
|
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.
|
|
The number of days to retain the rollback context for a background script execution
|
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.
|
|
The number of days to retain the rollback context for changes recorded during test executions
|
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.
|
|
The number of days to retain the rollback context for an 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.
|