Scheduled workflow deactivated by the server

Question

Hi, we have seen a possible network issue last night that has caused our Alteryx server to deactivate some workflows that were trying to run at the time of the issue.

It looks like the server has stopped the future runs of the workflow as it is being told by the AD that the user credentials are incorrect due to a wider business IT issue.

Is there anyway to stop this from happening?

Thanks

Ian

JohnBell · Answer

@Ian_Johnson

MichaelF

We're on version 2018.2, and we've had experiences where if the server goes down abruptly, any workflows in queue will become deactivated.  (It shows as completed).

My experience with AlteryxSupport, is that in an abrupt shutdown, the communication between the controller and worker gets corrupted, and the controller doesn't know when the "next run" is, and just shows it as completed.

The user will need to reset the schedule.

John