I've the problem, that my flows stop running because the connection has expired. (As far as I know: after 90 days).
Unfortunately, I got this information a week later - as a summary of all my failed flows.
So in fact, my flows weren't running for almost a week! This was not the first time, so I assume, that this will happen also in the future.
Also very bad: if I'm out of office for a longer period.
"You can update a connection that isn't working because your account details or your password changed"
Update a connection (microsoft.com)
@JesperdenBoer , @iwalker, @Toasteroven:I think you have the same problem/request, aren't you?
Hello @max81 That is true.
Hi Folks, in our case, in order to avoid this, we have a special service user which has non expired password date. May be this will give you some ideas to think about!
@diegoadum: that's of cause a solution for some processes, but we don't want to use too many service users. Also because that would make it really expensive if every service user need an additional license.
@diegoadum , I believe using a service account with a non-expiring password will not prevent this problem. We have just such a situation and we are still getting this issue. I think it's that the OAuth token issued to the connection (that was configured using the service/user account), is only good for 90 days. So even if the password never has to be change for the user/service account, any OAuth tokens generated by a "login" are going to go bad at 90 days.
So, I think @max81 's idea/request for a better way to manage/prevent such expiring tokens is a much needed item.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.