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.
Long-running transactions will generate sys_update_xml in the Default update set by the 'guest' user if the session expires before completion - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Long-running transactions will generate sys_update_xml in the Default update set by the 'guest' user if the session expires before completion
KB0695149

Long-running transactions will generate sys_update_xml in the Default update set by the 'guest' user if the session expires before completion


842 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

Long-running alters will generate sys_update_xml in the Default update set by the 'guest' user if the session expires before completion. This is a problem because these table-altering changes will not be captured in the correct update set, which will likely go unnoticed by the user. The form and list layout updates will be generated immediately in the user's update set, but the sys_dictionary and sys_documentation records will end up in the Default update set some time later.

Steps to Reproduce

Any long-running alter initiated from the UI is susceptible to this issue. It occurs most commonly on the CMDB and Task hierarchies.

Workaround

When creating a column from the Form/Layout Editor, the alter will be processed on a background thread instead of as a UI transaction, and thus is not susceptible to this issue. Alternatively, if you notice that you are required to log in again after waiting for a column creation/deletion/update to finish, simply check your update set and make sure the change was captured properly. If it was captured in the Default update set by 'guest' instead, make a non-schema-altering change to the record in order to re-capture it in your update set. An example of a non-schema-altering change would be flipping the read-only flag.


Related Problem: PRB1296866

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.