Symptoms

When trying to save a significant large Update Set with more than 100K update records as a local XML file using the 'Export to XML' UI Action on the Update Set [sys_update_set] table, the page loads a blank page or re-directs to the default page without exporting the XML file.

Cause

The issue is caused by the UI Transaction quota rule which is by default set to 5 minutes. More information about this quota rule can be found in the following documentation chapter: Default quota rule

Resolution

Increase the threshold of UI Transaction quota rule is one way to solve the issue BUT this impacts all UI Transactions for all users and might impact the instance performance.

We do advise to determine the changes to make in a single update set. Complete your update sets as you finish small to medium-sized tasks. As update sets get larger, it becomes harder to review them, takes longer to identify specific changes within them, increases the risk of conflicts with other update sets, and takes more time to preview and commit them.

However this is not applicable to publishing an application to update set. Publishing an application to update set creates an update set containing the current version of all application configuration records. This allows you to save a version of an application for compliance or backup reasons.

When having multiple Update Sets, you could make use of the Update Set Batching feature which enables you to group Update Sets together so you can preview and commit them in bulk.