Request item triggers event multiple times

[JenniferS1]

We have a request item that for some reason triggers an event 3 times when it is submitted. This then causes an email notification to get sent 3 times. The weird part is that this only happens when this one specific item is created. For every other item the event only gets triggered once and the email only gets sent once.

Any ideas?

[JonathanJacob]

A few other places to check:

1. Activity Log - do you see any updates to the activity log within seconds or minutes of each other, this could give you a tip as to what it modifying the record and causing the updates.

2. Event business rule- take a look at the business rules for that table specifically the 'table name events' which fires that specific event to be sure nothing was changed that could be causing this issue.

3. Check the Audit History via the right click > history, and see if you see any updates that are causing the event to fire.

4. Lastly you mentioned execution plans, check to be sure that current.update() is not used when not needed.

[jcraneNYC]

Thanks! Do you have other items with tasks going to the same groups as the ones above that are only sending once instead of twice? Is there a chance that there could be multiple notifications created that may be specifically targeting this group/task combination? Is this happening in both your prod and sub prod instances?

[JenniferS1]

Jon,

Yes we use the same execution plan for two other items and these create the same duplicate emails. It is happening in prod and sub prod instances.

[rajiv069]

Hi Jennifer,

This issue can be occur because of the following reasons:

1. Order of the Custom BRs written on the same table,

2. other customization related to variable calling though task table.

But most probably it would be related to Order of BR please check that in all of your customization and set this as per actual requirement need to work as per.

Thanks,

Rajeev Kumar

[Bhavesh Jain1]

Make sure there is no current.update() in any Run Script activity of workflow attached to that catalog item.

Best way to solve this problem is to start 'Debug Business rules'.

See the logs at the bottom the page loaded after the RITM is created. This will show all the business rules that are running.