Notification is getting triggered twice.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2023 11:19 PM
This is on sc_task table still its getting triggered 2 times.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2023 12:10 AM
Triggred at same time .
In condition and is used not or
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2023 12:53 AM
Hi, unfortunately partial screenshots don't add a lot od diagnostic value. Have you checked the email logs and confirmed that it is definitely the same notification that is being triggered twice? Most often the issue is multiple different notifications, with same or similar conditions, being triggered.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2024 08:57 PM
I just found the answer to this and posted on a different thread, but since this seems to be the most recent and concise thread about this problem, I thought I should post the answer here too:
There is a global business rule called "global events" that contains this line:
if (current.operation() != "insert" && current.comments.changes())
gs.eventQueue(name + ".commented", current, gs.getUserID(), gs.getUserName());
So if you're creating your own "task.commented" type of rule, you probably don't need to. This global already does that. If you really want to trigger your own event, you can use something other than "commented" in your BR and your notification definition.