Forum Discussion

jj44's avatar
jj44
Advocate I
9 months ago
Solved

Invoke pipeline error

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 ...
data engineering
Data Pipeline
  • v-achippa's avatar
    v-achippa
    9 months ago

    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

v-achippa's avatar
v-achippa
Community Support
9 months ago

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

  • jj44's avatar
    jj44
    Advocate I
    8 months ago

    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

    • Srisakthi's avatar
      Srisakthi
      Super User
      8 months ago

      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