This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi Colleagues,
Quesion: we have systematic issue with Fabric Data Pipelines (former Data Factory). Sometimes randomly, sometimes some specific conditions trigger a situation, when pipeline's activity fails, we have configured failure route to Teams Alert, and it doesn fire up.
Today, I observed, with one specific chat, I wasn't able 4/5 times to send an alert after pipeline's activity failed. When I tried the other chat, everything was fine. I would think, it is some specific problem with that specific chat, but we periodically have the same issue with the other pipelines, randomly.
Also, I didn't find that issue in the known issues. Does anybody face that as well? What the potential solution?
Disclaimer: recreation of the pipeline or activity doesn't help, I was playing with chats, channels.
On the attached picture, you may see the failed activity "Set variable 1", and after that, there is no further activity, but I was expecting to fire up Failure Alert. We use it as a part of Microsoft Fabric.
Solved! Go to Solution.
Can you share the overall Pic of the pipeline?
When you have multiple dependencies set across for diff activities to an activity,it functions as an AND.
Meaning team activity would be executed only if Set variable activity fails AND whatever conditions you have added for other activities
Hello @4iurchenko!
As it shown on your screen, you have lots of other activities befor the messaging, so they are all to be completed (or failed) to fire the message.
To solve it properly you have multiple options:
1. Set Teams message after each action, so then you will capture and deliver error message for all of them.
2. Have some variable to aggregate error messages into one body and then at the end of your pipiline (On completion) you can evaluate if it's not empty and post message.
Could you please check and reply if that what you are looking for?
BR, Taras
Hello @4iurchenko!
As it shown on your screen, you have lots of other activities befor the messaging, so they are all to be completed (or failed) to fire the message.
To solve it properly you have multiple options:
1. Set Teams message after each action, so then you will capture and deliver error message for all of them.
2. Have some variable to aggregate error messages into one body and then at the end of your pipiline (On completion) you can evaluate if it's not empty and post message.
Could you please check and reply if that what you are looking for?
BR, Taras
Thanks Nandan! I completely missed that point. Thanks a lot. I was believing the failure path is taken as OR. But yes, it seems it is AND.
Can you share the overall Pic of the pipeline?
When you have multiple dependencies set across for diff activities to an activity,it functions as an AND.
Meaning team activity would be executed only if Set variable activity fails AND whatever conditions you have added for other activities
Check out the June 2026 Fabric update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
| User | Count |
|---|---|
| 5 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |