Notification sent twice when a previous inbound action contains multiple updates even on different tablesSummaryIf you have a notification that triggers on insert/update, and this notification triggers twice for one update, it may be because of a duplicate of the event "notification_engine.process". If this is the case, it is needed to investigate why the event was triggered twice.Instructions- First, confirm that the event "notification_engine.process" was triggered twice: Go to the events list and look for such event at the time when the notifications were sent. You can confirm they are the same by comparing the values of parm1 and parm2. If they are identical you have your duplicates. - This event is generated when something happens on the related record (incident, case, etc.). Hop on the record and see how the event was generated. - It happens often that it was generated by an incoming email that updated the record. You will need to look at the inbound action that was activated, as this is where the issue lies. - In the inbound action's script, search for update() or insert(). Search also for "new Cart()" as it acts as an insert(). You should find many occurrences of update(). - Each update() will generate an event "notification_engine.process", even if the updates are on different tables. This generation of multiple "notification_engine.process" will send the same amount of notifications. What to do: - You can optimize the script to have only one update() - You can use notifications that trigger on customized events. Such customized event should be generated independently in the inbound action's script.