OAuth Token Refresh Failed in Fabric Pipeline — “DMTS_OAuthTokenRefreshFailedError” between Parent a

[aayushiharalal]

Hi everyone,

I’m facing an authentication issue in Microsoft Fabric pipelines and would appreciate some guidance.

🔧 Setup

• Environment: Microsoft Fabric workspace

• Pipelines:

  • Parent Pipeline: Uses Invoke Pipeline activity to call the child pipeline.

  • Child Pipeline: Contains a Wait activity.

  • All pipelines are in the same Fabric workspace.

    ⚙️ Issue Details

    The parent pipeline successfully starts, but when the invoked child pipeline runs, the execution fails with the following error:

     

    { "RunId": "411eb8e3-1c76-4b74-9d13-5def1bf2ad81", "IsCompleted": false, "Status": "Fail", "FailureType": "UserError", "Message": "Failed to resolve connection 'e7eca4a3-c203-441f-ad05-87a020d51cc3' referenced in activity run '411eb8e3-1c76-4b74-9d13-5def1bf2ad81'. ErrorCode: 'DMTS_OAuthTokenRefreshFailedError'. ErrorMessage: 'null'.", "StatusCode": 401 }

    What I’ve Checked / Tried

    1. Verified both pipelines are in the same workspace and use the same linked service.

    2. Still receiving the 401 error with DMTS_OAuthTokenRefreshFailedError.
    3. Error persists even after reauthorizing and republishing.

       Is there a known limitation when using Invoke Pipeline activity between parent and child pipelines

       
       Any insights, recommendations, or troubleshooting steps from others who’ve run into this with Fabric pipelines would be much appreciated!

       Thank you 
       — Ayushi Harlalka
       
       

       @grazitti_sapna, @Poojara_D12 , @tayloramy 

[v-venuppu]

Hi @aayushiharalal ,

Great to hear that its working from your end.I would suggest you to accept the response that guided you in solving the issue as a solution.It would be really helpful for others in the community who might be facing similar issues and can address them quickly.

Thank you.

[aayushiharalal · Accepted solution]

thank you it worked for me. I created a new Connection and changed connection in every activity.

[nielsvdc]

Great to hear you resolved it.

[v-venuppu]

Hi @aayushiharalal ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @nielsvdc for the prompt response.

I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.

Thank you.

[nielsvdc]

Hi @aayushiharalal, the error you get is not related to the invokation of the child pipeline, but rather a problem with a connection that is used within one of the pipelines.

The error message states the following:

"Message": "Failed to resolve connection 'e7eca4a3-c203-441f-ad05-87a020d51cc3' referenced in activity run '411eb8e3-1c76-4b74-9d13-5def1bf2ad81'

What is says is that the pipeline activity with id '411eb8e3-1c76-4b74-9d13-5def1bf2ad81' failed the authentication for connection with id 'e7eca4a3-c203-441f-ad05-87a020d51cc3'.

To resolve the problem, you might want to check the connections you use in the (child) pipeline.

You can also find these connection by clicking the Gear icon in the top right corner in the Fabric portal and then click Manage connections and gateways. On the connections in the status column, you can click the refresh button to validate if the connection is still working.

[aayushiharalal]

Hello @nielsvdc 

 Are you refering to the below Connections ?

[nielsvdc]

First check the connections within the pipeline, for example to a source or destination system in a copy data activity.

If you do not find a connection error within the pipelines, you can try the Fabric API Get Connections to search by the ID and see what connection it concerns.