Forum Discussion
TokenExpired 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.
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.
Do 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
I continued to have the same issue , but with an internal error message instead of the Access Token Expired Message. It was escalated to the product team and as of last night it appear to now be working correctly.
Message from Support below: