Duplicate email
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-06-2016 11:41 AM
We have an email notification that is triggered when the event approval.inserted is triggered. I have checked the email notification list and there is only one notification using this trigger, but for some reason in our Test environment, the email is being sent twice to each approver. This does not happen in our development environment. Does anyone know why it might be duplicating in one environment and not the other and how I resolve?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-06-2016 12:31 PM
If you only have 1 notification with that event, is the event getting triggered twice? You can check the event log and see if it's listed twice.
You can also check the email log and confirm it's the same notification going out twice. Maybe you overlooked a second notification.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-08-2016 12:30 PM
I had the same issue, but with a different email event. It was discovered that I was clicking through the state fields too quickly to generate the emails that go out when each state changes.
To fix, what I did was change the state on the form, then verify the email showed as sent in the email log, then went back to the form and changed the state again, then went back to the email log to verify as sent, etc., wash, rinse, repeat...
Thanks,
Laurie
Please mark Like, Helpful, or Correct as applicable!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-08-2016 12:58 PM
Weight Field in notification.
Set a numerical value for this notification's priority relative to other notifications with the same target table and recipients. The system only sends the notification with the highest weight. All other notifications are moved from the Outbox to the Skipped mailbox. The default value 0 causes the system to always send the notification (assuming the conditions are met).
For example, suppose a service desk agent adds a comment to an incident and shortly thereafter closes it. By default, these actions trigger both the Incident commented and Incident Closed notifications. However, since both notifications are from the Incident table and both notify the incident caller, the system only sends the notification with the highest weight, in this case the Incident Closed notification.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-12-2017 02:51 PM
We resolved this, but as it's been a while, I can't recall how we resolved it.