topic Re: Invoke pipeline error in Data Engineering

Invoke pipeline error

jj44 — Tue, 11 Nov 2025 11:00:43 GMT

Hi,

I have a number of pipelines in the same workspace, they all run successfully. I have created a master pipeline, to orchestrate these using the 'Invoke pipeline' activity.

When I try to run the master pipeline I get this error on the first activity
Failed to resolve connection 'xxxxxxx-xxxx-xxxx-xxxx-xxxxxxx' referenced in activity run 'xxxxxxx-xxxx-xxxxx-xxxxx-xxxxxxxxxxxxx'. ErrorCode: 'DMTS_OAuthTokenRefreshFailedError'. ErrorMessage: 'null'.

If I deactivate that activity, the next Invoke pipeline activity errors with the same type of error.

I have checked that the child pipelines all run when called directly, and I have checked and refreshed the connection being used in Settings.

I'm not really sure how to proceed...anyone got an suggestions?

Cheers,

Jeff

Re: Invoke pipeline error

v-achippa — Tue, 11 Nov 2025 13:20:40 GMT

Hi @jj44,

Thank you for reaching out to Microsoft Fabric Community.

Based on the error looks like here the runtime could not refresh the OAuth credential for a linked service. Please follow below steps:

Go to Manage --> Linked services, identify the linked service shown in the failed activity details, click Test connection and re-authenticate to restore the token and then rerun the master pipeline.
For a permanent fix, reconfigure the linked service to use a Managed Identity or a Service Principal with the client secret stored in key vault.
Make sure that the workspace managed identity or service principal has the required RBAC permissions on the target resource and Get or List access to key vault secrets.

After updating the authentication, test the connection again and re-run your master pipeline, this will permanently prevent the token refresh failures.

Thanks and regards,

Anjan Kumar Chippa

Re: Invoke pipeline error

jj44 — Wed, 12 Nov 2025 09:28:28 GMT

Hi @v-achippa

Yes, fully re-authenticating, rather than refreshing the connection did fix the problem.

Yes, I agree a more permanent solution is to use a service principal - on our list of things to be done.

Many thanks for your suggestions.

Jeff

Re: Invoke pipeline error

Srisakthi — Tue, 18 Nov 2025 07:02:40 GMT

Hi @jj44 ,

I have faced the same issue in invoke pipeline activity with Service Principal yesterday. It was throwing error as " Item with same key is already added".

After re-authenticating with same Service Principal details. It worked.

Microsoft needs to investigate this Invoke Pipeline error.

Thanks,

Srisakthi