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.
Duplicate notifications sent when a request is submitted - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Duplicate notifications sent when a request is submitted
KB0811700

Duplicate notifications sent when a request is submitted


2890 Views Last updated : Mar 11, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

Upon submitting a catalog request, the "Request Created" notification is sent twice.

Release

All releases

Cause

The notification triggers based on the conditions "Requested for is not empty AND Requested for changes" on insert and update of an REQ record. In the request item's workflow, there is a custom script that sets the REQ's requested for value from a variable. This update causes the notification's conditions to match again and the email is sent a second time.

Resolution

Se the requested for value in a before insert business rule which should run on the Request [sc_request] table. To do this, query the RITMs where the request field is the same as the current record, check to see if the variable has a value (or is present), and if it does, set the requested for with the value from the variable. Please note that 'before' business rules do not require to use current.update() as this can cause issues in the platform.


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.