Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Notification is triggering Multiple time for SLA and OLA

sayan-ghosh
Tera Contributor

Hello Team,

I have created a Notification for SLA,
But I have observed that the same Notification is triggering multiple time.
SLA is using the Default SLA Workflow.
Notification Condition:
==================

sayanghosh_0-1745091181356.png

sayanghosh_1-1745091323038.png


Event Log:
==========
It is taking different Instance with same Param1 value

sayanghosh_2-1745091485190.png


Same Notification Triggering multiple times:

sayanghosh_3-1745091646161.png

 


Best Regards

 



2 REPLIES 2

Robert H
Mega Sage

Hello @sayan-ghosh ,

 

This is because you have two Resolution SLAs on that Incident which are both above 75%.

So the SLA workflow is triggering an event for each SLA (the two in your Event Log dated 09:56).

And each of the two events is triggering a notification.

 

If you just need one notification you could add one more condition "SLA Definition.Type = SLA" (if the notification is end user facing) or OLA if it's meant for the operational teams.

 

Regards,

Robert

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @sayan-ghosh 

 

Agree with @Robert H  also on every SLA, there is a workflow attached which also triggers when the SLA is about to bereach, check if that can be a reason.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************