Additional notifications are adding at the time of SLA Breach.

[Ishaan Mishra1]

Dear Team,

I configured the SLAs on 'security incident' and added custom workflows(in workflows, I am calling events to trigger notifications to respective team) when it breaches.

So that, I created SLAs on ('Task SLA' table) and those are working fine, but the concern is 'incident' SLA breach notifications are also configuration on same 'task SLA' table, because of that- whenever 'security incident' was breaches both 'incidents' and 'security incidents' breach notifications are triggering to both teams, ideally this should not happening. Kindly suggest on the same.

Note: I added few conditions but still, breach notifications are triggering to both teams PFA,

Thank you.

[RaghavSh]

I your SLA a flow/workflow is defined, which fires the event and send the notification, copy that flow/workflow and make changes to that flow to fire different event, and based on that event send the notifications. 

[Ammad Satti]

Hi Ishaan

Can you verify if any other SLA definition condition is matching and multiple SLA's are getting attached?

Thanks