Notification Triggering Twice with the Same Timestamp

[SaipriyankaG]

We are observing an issue where the notification is being triggered twice with the exact same timestamp. Has anyone encountered a similar issue or can suggest possible causes and troubleshooting steps?

[Ankur Bawiskar]

@SaipriyankaG 

how is the notification configured?

may be some BR on that table has current.update() which is causing it to fire twice

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[SaipriyankaG]

Notification was configured through a  flow using the Create Record action on the sysevent table.

[Ankur Bawiskar]

@SaipriyankaG 

what's that notification about?

what's your actual business requirement?

[SaipriyankaG]

A notification is configured to trigger when an SLA reaches 100% breach. To achieve this, a Flow is used with a Create Record action that inserts a record into the sys_event table. However, the notification is being triggered twice for the same event, as shown in the above attached screenshot.