topic Re: Data Pipeline : Invoke Pipeline Issue in Pipelines

Data Pipeline : Invoke Pipeline Issue

Jester_3 — Wed, 09 Apr 2025 09:45:53 GMT

Hi,

In one of my workspaces I have 2 pipelines, one of which calls the other using the invoke pipeline utility.

The parent pipeline is successfully triggering the child pipeline which is then in turn running the notebooks utilities inside of it.

These notebook utilities all have a retry count of 2, meaning if they fail they'll retry.

My issue is that these notebooks fail on the first run but will succeed on the second run, that first failure is causing the parent pipeline to report a failure.

Even more strangely the child pipeline continues to run until it succeeds, even after a failure has been reported to the parent pipeline.

I have had this set up for months with no problems so I suspect something has changed.

This is the error that is reported from the child pipeline to the parent pipeline.

{"requestId":"XXX-XXX-XXX","errorCode":"TokenExpired","message":"Access token has expired, resubmit with a new access token"}

If someone could offer some advice I'd appreciate it.

Re: Data Pipeline : Invoke Pipeline Issue

nilendraFabric — Wed, 09 Apr 2025 12:54:49 GMT

Hi Jester_3

Microsoft has released a preview version that allows invoking pipelines across Fabric workspaces and monitoring child pipelines. Try using this once
https://learn.microsoft.com/en-us/fabric/data-factory/invoke-pipeline-activity

If the issue persists, it may be worth contacting Microsoft Support, as there could be a platform-specific issue or limitation that needs to be addressed

Re: Data Pipeline : Invoke Pipeline Issue

Jester_3 — Wed, 09 Apr 2025 12:58:25 GMT

Hi nilendraFabric

Thank you for the response, i'm already using the invoke-pipeline-activity.

Like you suggest, I think i'll contact Mircosoft Support.

Re: Data Pipeline : Invoke Pipeline Issue

v-sathmakuri — Thu, 10 Apr 2025 19:20:13 GMT

Hi Jester_3 ,

Thank you for reaching out to Microsoft Fabric Community.

In the "Invoke Pipeline" activity, please ensure that the "Wait on completion" option is checked so that the parent pipeline only succeeds after the child pipeline completes successfully. PFBS for reference.

I tested this by creating a script that fails on the first run and succeeds on the second. Then, I called this pipeline from another pipeline using the "Invoke Pipeline" activity with "Wait on completion" enabled, and the parent pipeline completed successfully.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

Thanks & Regards,

Rekha,

CustomerSupportTeam.

Re: Data Pipeline : Invoke Pipeline Issue

Jester_3 — Fri, 11 Apr 2025 08:14:38 GMT

Hi v-sathmakuri

I checked that the wait for completion setting was enabled on the invoke-pipeline-activity and it was.

Thanks for the suggestion.

Re: Data Pipeline : Invoke Pipeline Issue

v-sathmakuri — Fri, 11 Apr 2025 08:27:09 GMT

Hi Jester_3 ,

Could you please check whether the pipeline you're trying to run has succeeded? Also, please review the latest run of this pipeline using the Monitor option in Fabric

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

Thanks & Regards,

Rekha,

CustomerSupportTeam.

Re: Data Pipeline : Invoke Pipeline Issue

Jester_3 — Fri, 11 Apr 2025 08:49:08 GMT

Hi v-sathmakuri

I have checked the monitoring hub and can see that the child pipeline is correctly completing but a failure is still being reported to the parent pipeline.

In this instance the first fail from tickets is causing main pipeline to fail, but the fresh service pipeline runs until completion and has succeeded.

Thanks

Re: Data Pipeline : Invoke Pipeline Issue

v-sathmakuri — Fri, 11 Apr 2025 09:42:46 GMT

Hi Jester_3 ,

I have reproduced the same scenario. Please refer to the screenshot below for reference. In this case, Pipeline 5 serves as the main pipeline, while Pipeline 1 acts as a child pipeline, within which Notebook 1 is called. Both pipelines executed successfully after enabling 'Wait on completion'

Could you please share the screenshots showing how you configured both the child and main pipelines? This will help me suggest better solution.

Thanks & Regards,

Rekha,

CustomerSupportTeam.

Re: Data Pipeline : Invoke Pipeline Issue

Jester_3 — Fri, 11 Apr 2025 10:13:38 GMT

Hi v-sathmakuri

This is the topology of my main pipeline :

This is the topology of my child pipeline :

The notebooks inside of the child pipeline have 2 code cells:

The first one is a spark sql cell that deletes the old table from the lakehouse
The second one is a pyspark cell that runs the python that gets the new data and creates a delta table in the lakehouse.

Hope this helps.

Re: Data Pipeline : Invoke Pipeline Issue

v-sathmakuri — Fri, 11 Apr 2025 10:48:36 GMT

Hi Jester_3 ,

Thank you the quick response.

Could you please ensure that the 'Wait on completion' setting is enabled on the Invoke Pipeline activity, and also confirm that all notebooks in the child pipeline complete successfully? From my end, this setup appears to be working correctly.

Additionally, please check which specific activity or step is causing the failure in the parent pipeline. This will help isolate whether the error is coming from the child pipeline or the

invocation logic.

If the notebooks are intermittently failing on the first run and succeeding on retry, consider adding try-catch blocks within the notebooks to gracefully handle transient errors (like token expiration), so they don’t fail on the first attempt

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

Thanks & Regards,

Rekha,

CustomerSupportTeam.

Re: Data Pipeline : Invoke Pipeline Issue

Jester_3 — Fri, 11 Apr 2025 12:18:40 GMT

Hi v-sathmakuri

Wait on completion is enabled on all invoke-pipeline-activity nodes.

There is no error reported from the child pipeline :

There is an error reported from the initial invoke pipeline in the main pipeline :

This is the message that is displayed for that failure

"message": "Access token has expired, resubmit with a new access token".

I have no idea what access token its referencing.

Hope this helps narrow it down.

Like I said in my initial post i've ahd this set up for some time with no issue so i don't understand why its happening now, logically it shouldn't be.

Re: Data Pipeline : Invoke Pipeline Issue

v-sathmakuri — Mon, 14 Apr 2025 05:20:31 GMT

Hi Jester_3 ,

The pipeline is failing because the child pipeline is taking longer to complete. To resolve this, I switched to using the Invoke Pipeline (Legacy) activity instead of the Invoke Pipeline (Preview) activity, and the pipeline succeeded.

Please use Invoke Pipeline (Legacy), as the Preview version relies on a linked service, and the access token used by that linked service is expiring during long-running executions.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

Thanks & Regards,

Rekha,

CustomerSupportTeam.

Re: Data Pipeline : Invoke Pipeline Issue

Jester_3 — Mon, 14 Apr 2025 10:47:50 GMT

Hi v-sathmakuri

You were correct it was an issue with using the preview version of invoke-pipeline.

Thanks for your help.