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.
Incorrect condition in a business rule firing the event may send multiple notifications - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Incorrect condition in a business rule firing the event may send multiple notifications
KB0755067

Incorrect condition in a business rule firing the event may send multiple notifications


390 Views Last updated : May 8, 2023 public Copy Permalink
KB Summary by Now Assist

Issue

Incorrect condition on the business rule which fires the event specified on the email notification may send duplicates.

Cause

When there is an email notification defined to run when a specific event is fired, and the business rule which fires the event has an incorrect condition specified, it will skip that condition and evaluate the remaining, if any. This may lead to send out multiple notifications.

Resolution

In a use case example where there is a Business Rule on the [sys_history_set] table with the Advanced Condition:
!current.id.demand_manager.changes() && (current.updated != previous.updates)

Notice the second part of the condition which has:
current.updated != previous.updates

There is no "updated" field in the "sys_history_set" table. The correct statement should be:
current.updates != previous.updates


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.