Copy of default SLA flow inside a security incident application not triggering breach notification

[gthapa]

Hello community,

So I understand that a Default SLA flow designer in global scope creates and triggers a notification for events created inside the notification such as - 'SLA warning parm' and SLA breached parm'. So, I copied the same flow designer with a new label and saved it in a Global scope. Now I have added that flow inside my custom-built SLA inside the security incident response application. Now, once I create a security incident it should create an email notification of SLA breach in my email notification which it currently is not doing. So. I can't find a reason why it's acting that strange. Can someone help figure this out who has faced similar incident?

[Mark Manders]

You will need to share more about your setup. You mention that the email isn't triggered. What does the flow execution say? Is the flow triggered but the notification not created? Is the SLA not triggered at all? Is the email created, but not sent, or isn't it created at all? What are the triggers for the email? 
How is the flow running? Are you triggering the email on the incident or on the SLA record and does the recipient has access to that record?

[gthapa]

Hi Mark thanks for responding. This has been resolved.

[Mark Manders]

It will help others with the same question/issue if you also provide the solution to the issue, now it is resolved.