Notification Triggering Twice with the Same Timestamp

[SaipriyankaG]

We are observing an issue where the notification is being triggered twice with the exact same timestamp. Has anyone encountered a similar issue or can suggest possible causes and troubleshooting steps?

[Ankur Bawiskar]

@SaipriyankaG 

how is the notification configured?

may be some BR on that table has current.update() which is causing it to fire twice

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Tanushree Maiti]

Hi @SaipriyankaG 

Refer KB: KB2923037 Duplicate Email Notifications Are Generated for an update on a table 

Cause

The issue was caused by a current.update() call within a Custom Business Rule. This forced an additional database save of the same record immediately after the initial insert, effectively writing the record twice in the same transaction.

This double-save triggers the events twice, generating two sets of email notifications. The OOB Ignore Duplicates rule catches the second set and marks them "send-ignored", but the first set is already sent, resulting in receiving duplicate emails.

 

 

Resolution

Modify the custom Business Rule as follows:

 Step 1: Change the Business Rule timing and order

• Set When: Before
• Set Order: 999,999

Changing the rule to Before ensures the Business Rule logic runs within the same transaction as the record insert, preventing an additional save from being triggered. This ensures that, the events fire only once, eliminating duplicate email notifications. Setting the order to 999,999 places this rule last in the Before rule execution sequence, avoiding unintended side effects on other Before rules.

Step 2: Remove (current.update())

current.update() forces an additional save of the same record, which re-triggers Business Rules and generates duplicate events. Removing it eliminates the second save cycle entirely.

[dellyou088]

Troubleshooting steps:

1.Open the mail and check , from where it is getting triggered if it is triggering from event check for event log.

2.Go to studio and search for that event in the search bar to find from where it is configured or written.

3.If it is from any flow check the flow execution history to find.

More information is appreciated.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards