How are you all handling Teams notifications for PL activity failures - especially with reruns?

[samuvva]

I'm trying to build a reliable and smart way to send a Teams notification if any activity in my Fabric pipeline fails. The challenge is making sure it works well for both sequential and parallel flows - and also handles partial reruns correctly.

Here’s roughly what I’ve done:

• I set a PipelineStatus variable to "Success" at the start of the pipeline.
• For all final activities in each branch, I connect their onFailure and onSkip paths to a shared SetVariable activity that sets the pipeline status to "Failed", and then forward that to a central Wait activity.
• All final activities - regardless of outcome - are also connected to the same Wait activity using onCompletion. From the Wait, I trigger a Teams notification using onCompletion, which checks the PipelineStatus to determine whether to send a failure alert.
• This works well in most cases - even if something fails midway, the notification is still sent.
• However, there's a problem during partial reruns: Previously successful activities get marked as skipped, which still routes to the failure path and triggers the Teams alert - even if the rerun was actually successful.

Looking for ideas or patterns to avoid this false failure notification during reruns.

Has anyone come up with a better pattern for this? Would love to hear how others are approaching it.

[v-csrikanth]

Hi @samuvva 

It's been a while since I heard back from you and I wanted to follow up. Have you had a chance to try the solutions that have been offered?
If the issue has been resolved, can you mark the post as resolved? If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
Looking forward to your reply!

Best Regards,
Community Support Team _ C Srikanth.

[v-csrikanth]

Hi @samuvva 

I wanted to follow up since I haven't heard from you in a while. Have you had a chance to try the suggested solutions?
If your issue is resolved, please consider marking the post as solved. However, if you're still facing challenges, feel free to share the details, and we'll be happy to assist you further.
Looking forward to your response!

Best Regards,
Community Support Team _ C Srikanth.

[v-csrikanth]

Hi @samuvva 

Thank you for being part of the Microsoft Fabric Community.

As highlighted by @nilendraFabric @rohit1991 , the proposed approach appears to effectively address your requirements. Could you please confirm if your issue has been resolved?
If you are still facing any challenges, kindly provide further details, and we will be happy to assist you.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.

[rohit1991]

Hi @samuvva ,
You're tackling a common but tricky scenario, and it sounds like you've already set up a thoughtful pattern. The issue with partial reruns falsely triggering failure notifications due to skipped activities is a known challenge in Fabric pipelines. One potential refinement is to track only genuinely failed activities rather than treating both onFailure and onSkip the same way.

You might consider creating a dedicated failure-tracking mechanism using custom logging or activity output inspection. For instance, rather than relying solely on onSkip, use an If Condition activity after each branch to evaluate the actual run status of critical steps—this way, you can isolate true failures from skips that occur due to partial reruns. Additionally, tagging pipeline runs with metadata (like a unique run ID or manual rerun flag) can help filter notifications so that alerts are sent only when the pipeline ends in an actual failure. Using logic apps or Power Automate for more advanced alert handling may also offer better control, such as evaluating execution logs before triggering a Teams message.

Passionate about leveraging data analytics to drive strategic decision-making and foster business growth.

Connect with me on LinkedIn: Rohit Kumar.

[nilendraFabric · Accepted solution]

Try  this

Wrap child pipelines in a parent pipeline using Invoke Pipeline activities.
• Logic:
• Parent pipeline tracks the overall status of child pipelines.
• Reruns of individual child pipelines won’t affect the parent’s notification logic.
• Teams notifications are triggered only from the parent pipeline’s final status.