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.
Opening a particular record times out because of the Activity Stream taking too long - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Opening a particular record times out because of the Activity Stream taking too long
KB0791687

Opening a particular record times out because of the Activity Stream taking too long


1738 Views Last updated : Feb 26, 2025 public Copy Permalink
KB Summary by Now Assist

Description

If the Activity Stream field has been added to a form and that form is used for records that have thousands of audit entries, then the form will load slowly the first time a user looks at the form.

This is because the Activity Stream is dependent on the creation of a History Set. History Sets are a way of collecting all the different activity types into a temporary table that "caches" a certain result based on domain, language, timezone, and date format. The whole History Set must be built, regardless of what setting has been configured to restrict the fields displayed in the Activity Stream properties for that table (e.g. glide.ui.incident_activity.fields).

For example, if a customer has over 15,000 audit entries related to a single record it can take over 1 minute to build the History Set the first time.

Steps to Reproduce

In an affected instance

  1. Create 15,000+ audit entries related to an incident (or any task record).
  2. If you do step #2 through the backend, make an update to the incident so that the HistorySet gets updated.

Notice that it takes about 16 seconds to load the form the first time.

For an instance with many millions of audit records, this takes substantially longer - over two minutes - especially if they have Table Extension implemented on the sys_audit table.

Workaround

This is expected behavior and by design. If you are affected by this issue, please try any of the following workarounds:

  1. You can open the record on a different view that does not contain the work_notes so it does not load the activity stream
  2. You can remove the work_notes from being displayed on the default view
  3. Delete the sys_audit records on the particular record column that has a lot of audit records in order to view it with the work notes

Related Problem: PRB1292391

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.