Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Unable to export a large Update Set as a local XML file using the 'Export to XML' UI Action, the page loads a blank page or re-directs to the default page. - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Unable to export a large Update Set as a local XML file using the 'Export to XML' UI Action, the page loads a blank page or re-directs to the default page.
KB0712380

Unable to export a large Update Set as a local XML file using the 'Export to XML' UI Action, the page loads a blank page or re-directs to the default page.


2273 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

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.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.