Unique Key violation detected by database ((conn=999850) Duplicate entry '781b08101b739450c91421b4bd4bcb90' for key 'PRIMARY')
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-07-2020 05:45 AM
We have a Business Rule that creates an Incident from a New Call. When it runs, it gives the following error message, but continue to create the incident as expected:
"Unique Key violation detected by database ((conn=999850) Duplicate entry '781b08101b739450c91421b4bd4bcb90' for key 'PRIMARY')"
I found many pointers from this Community advising against the use of "current.update()" on Business Rules. I then commented this part out of my script, but I still get the same error.
Could you please advise what else could be causing this error.
Background info: This Buiness Rule was converted from a UI Action where everything was working fine, but the same script gives the error on a Business Rule.
- Labels:
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2020 12:29 AM
Thank you very much to Asifnoor and Jack for your effort in trying to assist me on this issue. We finaly got it resolved as follows:
We enabled Debug Business Rule (Details) and started by looking into the business rule one by one that ran, you can ignore the ones that are skipped. We found one business rule that had current.update(). When we deactivated that business rule, the error disappeared.
So, it turned out that we didn't have to remove current.update() on our problem business rule only, but also to others that may have been triggered.