hi there,
after a workflow is published to the server using SP Input and Output tool the workflow fails to this error:
Failed to connect to SharePoint
AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2022-12-16T16:44:12.0681632Z and was inactive for 90.00:00:00.
We connect using the option "Sign In via Internet browser" and we publish the workflow using a superuser.
Do you know if there is a fix on this? For instance something that our IT dept should do in order to not make the token expire?
Thansk
Luca
Hey @lzanotti, looking at this idea SharePoint Token Auto Refresh - Alteryx Community it does look like there may be options your IT can set to stop the token timeout.
hi @IraWatt thanks for quick reply, I have followed the link but I does not provide any fix. Does it mean that are we waiting Alteryx to fix this at their end?
Thanks
Luca
@lzanotti I was just pointing out that if you ask your IT there maybe the option to ask them to stop the tokens timing out. Another option is to run the workflow more often as if the token is active it sounds like it wont time out looking at that error message.
hi @IraWatt unfortunately it seems there is no way to extend the lifetime token, however I have a fundamental question: why should expire if was running daily in the Gallery?
@lzanotti interesting question, it is strange if its running daily and the error message says its inactive. You could try submit a case to Alteryx support Support - Alteryx Community to see if there is a solution.
The access tokens generally have lifetime for an hour and refresh tokens have lifetime of 90 days. The refresh tokens can be used to generate new access token and a new refresh token. Trying to sign via Internet Browser will provide an access token which will expire in an hour. That could be reason of failure here
We've done a lot with sharepoint. The tokens are only good on the machine where they were entered and expire after 90 days. We have to (1) limit the workflow to run on a specific worker and (2) enter the user credentials using Designer on that machine before we publish. We have a process in place that identifies scheduled jobs that are 80+ days past entry and soon to expire. Note there is a sentence on the tool documentation that it is not for server, but we need to use it on server so accommodate the nuisance.