I currently am using a flow that is triggered on a CDS record change and am utiliing the Terminate action to cancel the run when I know the record change does not relate to the current workflow (and as such would create an actual failure).
However the built-in flow notifications treat this cancellation as an actual failure, and as such I cannot rely on these notifications as a way to determine if something actually has gone wrong.
My current work-around is to create an "On Failure" parallel branch that sends an email...but this method is tedious as I would need to put this "on failure" branch on every possible action that could fail..
AnupmaSharma on: Separate Triggers and Actions in Data Loss Prevent...