How to send failure email in pipeline without connecting to each activity?

[Scott_Powell]

Hi, I've got a pipeline that includes a bunch of different activity. I'd like to add Outlook activity to send emails for the start time of the pipeline, success time of the pipeline, and failures of the pipeline.

The start time and success time are easy - I just add a Outlook activity to the very start of the pipeline, and add another at the end of the pipeline connected to the last operator via the "on success" connection.

In theory I "could" add a failure Outlook activity by connecting to each and every activity using the "on failure" connection - but this makes the pipeline impossible to read - it ends up with lines everywhere. Is there a better way to do this so I don't have to connect the failure activity to each and every other activity in the pipeline?

Thanks!

Scott

[NandanHegde · Accepted solution]

Hey,

In case if you want to capture error message of every activity, then connecting each activity and getting the error message if any is the way as stated in eblow blog :

https://datasharkx.wordpress.com/2024/02/17/error-logging-and-the-art-of-avoiding-redundant-activiti...

But f you want to avoid this, then you can have your logic in a pipeline and call that pipeline via execute activity in another pipeline to directly get the error message.

But you would get only 1 error message of an activity and not all failed activity messages

[v-cboorla-msft]

Hi @Scott_Powell 

Thanks for using Microsoft Fabric Community.

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

Thanks.

[Scott_Powell]

I've accepted the original advice as the solution - but it's really suboptimal to have to join every single activity with the fail status to the failure email step. And I'm not a fan of putting pipelines inside of other pipelines - it really obfuscates what's going on.

I'll try to create an Idea to have a "generic fail" where you don't have to specifically wire it to every step, but if a failure happens it would automatically let you know.

Thanks,

Scott

[NandanHegde]

Unlike PaaS Azure data factroy, you can have Status REST API or integrate with log analytics and get those details, Fabric data pipelines has yet not matured to that state as of now.

So for now this is theonly way to get all the details , but you can sure submit an idea for the product team to brainstorm on