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.
relationship.rollup events backlog caused because of change in OOB business rule "cmdb synch event" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • relationship.rollup events backlog caused because of change in OOB business rule "cmdb synch event"
KB0785192

relationship.rollup events backlog caused because of change in OOB business rule "cmdb synch event"


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

Issue

A large amount of events (over 4 million) created with name="relationship.rollup" creating a backlog in the sysevent table leading to delay in the processing of other events in the queue.

Cause

The reason for the creation of so many events with name="relationship.rollup" was the Out of the box business rule "cmdb synch event"

In out of the box instances, this business rule has the INSERT || UPDATE || DELETE options unchecked in the "When to run" section. If you have all these options checked, whenever any of these operations happen on the cmdb_ci table, the business rule will be triggered, leading to millions of events getting generated.

These options should be used very carefully. Enabling them on a large table like cmdb_ci will surely lead to the creation of millions of these events which would create event queue alerts because of the backlog.

Please find below screenshot of script action for relationship.rollup events which is also Out of the box.

Resolution

  1. To clear out the backlog, Error out these events from the sysevent table so other events can get processed
  2. To avoid this issue to reoccur uncheck INSERT || UPDATE ||DELETE options in the "When to run" section for the business rule "cmdb synch event" which is also the Out of the Box setting.

Note: If, for some reason, the options cannot be unchecked as a long term solution then open a new case with Technical Support to see the need to perform a relationship rollup.


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.