Forum Discussion

marslan1's avatar
marslan1
New Member
3 months ago

Dynamic Failure Messages from 1 Activity

Hey,

 

I have a pipeline contains over 150 NB, Semantic Mode, and Power BI. Its also growing. I want just 1 activity that I can connect with all and it would be dynamic enough to tell me exactly which NB/Semantic/PBI failed without using hard code functions (I can use dynamic functions tho).

 

I don't think that's available today in MS Fabric, is it?

8 Replies

  • I haven't test it out yet, I will test and let you know here if this solution worked.

    • v-kpoloju-msft's avatar
      v-kpoloju-msft
      Community Support

      Hi marslan1

      Could you let us know whether the solution mentioned above worked for you? If you encountered any issues or have feedback, please share your experience so we can assist further if needed.

  • Hi marslan1
    Thank you for reaching out to the Microsoft Fabric Community Forum.

    Yes, this can be handled in Microsoft Fabric without creating separate failure logic for all 150+ activities. Since your pipeline is continuously growing, the better approach would be to use a centralized failure-handling activity and connect all Notebook, Semantic Model, and Power BI activities through the “On Failure” path. Inside the common handler, you can use dynamic expressions to capture details such as the failed activity name, error message, status, and activity type instead of hardcoding values for each activity. This makes the solution much easier to maintain and scale.

    For a more enterprise-level design, you can also consider a metadata-driven approach using Lookup + For Each activity, where activities are managed from a config table or JSON file instead of manually maintaining hundreds of pipeline activities. Fabric currently does not provide a fully automatic global error handler, but the above approach is the most scalable and commonly used pattern for centralized monitoring and dynamic failure logging.

    Refer these links:
    1. https://learn.microsoft.com/en-gb/azure/data-factory/tutorial-pipeline-failure-error-handling? 
    2. https://learn.microsoft.com/en-gb/azure/data-factory/control-flow-expression-language-functions? 
    3. https://learn.microsoft.com/en-gb/fabric/data-factory/pipeline-overview? 

    Hope this helps. If you have any questions regarding this, please feel free to reach out us. We will be happy to help.

     

    • v-kpoloju-msft's avatar
      v-kpoloju-msft
      Community Support

      Hi marslan1

      Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

      Thank you.

       

  • That Failure activity will give me a notification on my email / Teams? - my believe is, its just notify you in MS Fabric and I / we don't check notifications inside the Fabric every day.

    • v-kpoloju-msft's avatar
      v-kpoloju-msft
      Community Support

      Hi marslan1
      Thanks for the update.

      Yes, you are correct, the default failure handling inside Fabric mainly helps with monitoring within the Fabric experience itself, and many teams do not actively check Fabric notifications every day. In your scenario, since you have 150+ activities and need proactive monitoring, relying only on Fabric notifications would not be ideal.

      A better approach would be to keep the centralized failure handler and integrate it with external notification services such as Microsoft Teams, Email, Logic Apps, or Power Automate. Using the common “On Failure” path, you can dynamically capture details like failed activity name, pipeline name, error message, and execution status, then send those details automatically to Teams or email notifications.

      Hope this helps. If you have any questions regarding this, please feel free to reach out us. We will be happy to help.

       

      • v-kpoloju-msft's avatar
        v-kpoloju-msft
        Community Support

        Hi marslan1

        Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

        Thank you.