Forum Discussion

alloowishus's avatar
alloowishus
Icon for Helper I rankHelper I
1 month ago
Solved

Will the current "invoke pipeline" activity be fixed?

I found out on google that the new invoke pipelines can suppress failures from child invoke pipelines. I have experience this firsthand. Will fabric fix this problem in the new activity before retiring the legacy one? It is much more elegant to capture the error output of a master pipeline than to capture all the individual failures of the child pipelines.

workspaces

4 Replies

  • suparnababu8's avatar
    suparnababu8
    Icon for Super User rankSuper User
    30 days ago

    Hi alloowishus​ 

    I agree with you. Yes, MSFT Fabric team is aware of  the issue with the new Invoke Pipeline activity suppressing child failures and they are planning fior the fixes before the legacy activity is retired. The same information we can see in community chats as well.

    But as of now there nis no official confirmation, when they are going to fix this. Please check the Fabric road map. Adding few links below it may helpas you

    Data Pipeline : Invoke Pipeline Issue | Microsoft Fabric Community

    Microsoft Fabric Release Plan | Microsoft Fabric Community

    Microsoft Fabric Roadmap

     

    Thank you!

     

     

  • ShivekMaharaj's avatar
    ShivekMaharaj
    Icon for Community Champion rankCommunity Champion
    23 days ago

    Hi alloowishus​,

    I would add one caution around the expected fix/retirement timeline.

    Microsoft's current Invoke pipeline documentation still documents both activities:

    • Invoke pipeline (Legacy), for Fabric pipelines in the same workspace
    • the newer Invoke pipeline, which adds cross-workspace/ADF/Synapse invocation and child-pipeline monitoring


    I could not find a current Microsoft Learn, roadmap, release-plan or known-issues entry that gives a retirement date for the Legacy activity, or an official commitment that the child-failure propagation behaviour will be fixed before that retirement.

    I also do not see Microsoft documenting "child pipeline fails but the parent succeeds" as intended behaviour.

    So if the Legacy activity currently gives you the failure propagation you require and your parent/child pipelines are in the same workspace, I would be comfortable keeping it temporarily rather than migrating solely on the assumption that it is about to be retired.

    If you need the newer Invoke Pipeline activity for cross-workspace invocation, I would validate the actual child run independently for now. The Fabric Monitoring Hub supports upstream/downstream pipeline navigation, which makes it easier to confirm the child run's real status even when the parent status is misleading.

    For automated production handling, I would also open a Microsoft Support case with a minimal reproduction and both the parent and child Run IDs. That gives the product team something concrete to correlate if this is the same failure-propagation issue.

    So my current understanding is:

    • the newer Invoke Pipeline activity is the strategic activity and its remote invocation capabilities are already GA;
    • Legacy Invoke Pipeline is still officially documented and available;
    • I cannot find an official published fix date or Legacy retirement date for this specific issue.


    If anyone has a Microsoft roadmap/work-item reference confirming the fix timeline, that would be useful to add here.

    AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.

Related content