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.
Advocate II 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.
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."
- jankuc
Wow, you have much faster MS Support than we do. I've filed it even before posting here.
V-yubandi-msftCommunity Support
Hi 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.