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.
14 Replies
This exact issue has just occured for me too. Started last night. Same scenario; data pipeline uses the invoke pipeline activty to run another pipeline which takes 90 minutes to run. The invoked pipeline is successful , but the initial pipeline's "Invoke Pipeline" activity fails with the message below.
{"requestId":"xxxx","errorCode":"TokenExpired","message":"Access token has expired, resubmit with a new access token"}
I think there might be an error. When DF is polling for the status of the invoked pipeline, they are signing it with a token that expires (lets say after 60minutes) and after that, they dont get the memo that the invoked ppln finished successfuly, but get an error with forbidden access, or some such.
Yes I fully agree. I've raised a MS Support ticket. If I get a resolution I'll let you know.
Same problem here, let's hope it will be fix at the end of this month.
The workaround needing to deploy a notebook that check pipeline or notebook status through the API seem not ideal solution.
