Forum Discussion
Advocate ITokenExpired Error Fails Invoke pipeline activity even when underlying pipeline finishes fine
Response from Microsoft Support:
PG team has identified the cause, this issue is linked to the use of OAuth connections for pipelines, resulting in expired access tokens that require resubmission with new tokens. The bug work item is already deployed. It should get fixed by the end of this month.
Respnse from Microsoft: "We already have a known issue reported for the similar issue, our Product Team is investigating the issue and I'll let you know when the fix is deployed."
Community SupportHi jankuc ,
Thank you for the update. Once you receive further information from support, kindly share it here. It will be helpful for others in the community who may be facing similar issues.
Regards,
Yugandhar.
Response from Microsoft Support:
PG team has identified the cause, this issue is linked to the use of OAuth connections for pipelines, resulting in expired access tokens that require resubmission with new tokens. The bug work item is already deployed. It should get fixed by the end of this month.
jankucDo you still see these issues today? For us it seems MS has finally deployed some fix and the Invokes don't fail for us.
That is good news jankuc. I was contacted by Microsoft yesterday to ask if I was still seeing the issue. I responded with this timeline of failures. So hopfully they applied a fix yesterday or today and I'll stop seeing failures moving forward.
09/04/2025 – Fail - Access token has expired, resubmit with a new access token
11/04/2025 – Success
12/04/2025 – Success
13/04/2025 – Success
14/04/2025 – Fail - Access token has expired, resubmit with a new access token
15/04/2025 – Fail - Access token has expired, resubmit with a new access token
16/04/2025 – Fail - Access token has expired, resubmit with a new access token
17/04/2025 – Success
18/04/2025 – Success
19/04/2025 – Fail - Access token has expired, resubmit with a new access token
20/04/2025 – Fail - Access token has expired, resubmit with a new access token
21/04/2025 – Fail – Other Unrelated Issue.
22/04/2025 – Success
- ananthkrishna99
We are facing the same issue again. the Pipeline Copy acitvity is failing after ~90mins of execution while writing data into Lakehouse. It is throwing Lakehouse operation failed for: Operation returned an invalid status code 'Unauthorized'.
- jankuc
Thanks for info. We already have a workaround. A notebook that runs if the InvokeActivity fails which gets the status of the pipeline run through rest api. Looking forward to not needing to use that workaround in the future.