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.
Large update set does not commit - clicking on the Commit button does not initiate commit process - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Large update set does not commit - clicking on the Commit button does not initiate commit process
KB0622770

Large update set does not commit - clicking on the Commit button does not initiate commit process


1683 Views Last updated : Jan 10, 2023 public Copy Permalink
KB Summary by Now Assist

Description

Committing update sets with tens of thousands of updates in them can fail. Clicking the Commit button does not start the process - the progress bar for the commit process does not appear.

Steps to Reproduce

 

  1. Create a large update with 40.000+ customer updates.
  2. Mark the update as complete.
  3. Retrieve the large update set into the target instance.
  4. Ensure that the UI Transaction Quota Rule is configured as base system ("out of the box").
  5. Preview the update set.
  6. Press the Commit button once.
  7. Wait for five minutes (this is the UI Transaction Quota rule cut-off time).
    Note that, instead of the progress worker bar showing the stage of the commit process, the transaction counter starts counting on top of the form until the transaction is cancelled by the UI Transaction Quota Rule.

Workaround

As a general recommendation, avoid excessive merging of update sets. Update sets need to be manageable when it comes to the number of customer updates they contain.

If, however, update sets were already merged and the final update set is causing this issue, review the UI Transaction Quota rule. Exclude the update set commit UI transaction from the rule to allow the instance to process the transaction that will start the commit process:

  1. Navigate to System Definition > Transaction Quota Rules.
  2. Search for SYS_ID of 88fe39123701200024d1973ebebe5dfd.
  3. Update the condition on the record to include: [URL] [does not contain] [sysparm_processor=UpdateSetCommitAjax].

Related Problem: PRB961280

Potentially Seen In

There is no data to report.

Fixed In

Jakarta

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.