That makes sense, around 2 weeks ago we experienced the same issue, our
scenario failed with a message that the user was not authorized even
though the user credentials had not changed, we re-authorized and I did
open a WF support ticket on it and they are aware of it effecting a few
customers at the same time. It seemed like a one-time glitch thankfully.