2022.1.1.30569 Patch Release Update

The 2022.1.1.30569 Patch/Minor release has been removed from the Download Portal due to a missing signature in some of the included files. This causes the files to not be recognized as valid files provided by Alteryx and might trigger warning messages by some 3rd party programs. If you installed the 2022.1.1.30569 release, we recommend that you uninstall it, and then install the latest 2022.1.1.30961 version.

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.

Weird Server Reply error message

12 - Quasar

Today we had some Scheduled workflows fail on Alteryx Server with the error Weird Server Reply.

It looks like this happened for workflows that had email outputs, either with output tools or event triggered emails (on completion or error).

The issue seems to be occurring sporadically.


Has anyone seen this error before and can explain what might cause it?


wwatson_0-1594028461001.png Output tool email

wwatson_1-1594028538478.png Event triggered email




12 - Quasar

Also getting the error when running the WF in designer.

12 - Quasar

The issue was with the SMTP mail server rather than Alteryx.


The error message could have been more helpful though.

5 - Atom

How did you troubleshoot this? What were your steps to resolve the issue?

5 - Atom

We are experiencing the same thing both on Alteryx Designer and Alteryx Server. 


We have email event "After Run" set up for all our flows. Most of the flows have no problem except this particular flow runs more than 1 hour is experiencing this "Weird Server Reply" error. If I put some of tools in a container and disable the container to cause the flow finish, say 20 minutes, then the problem goes away. It seems to relate to how long the flow runs. 


Also, if I add an email tool at the end of the flow, then the email tool experience the "Weird Server Reply" error but the "After Run" email event gets executed without error. So, it seems the first email action takes the hit, then, subsequent email action gets run ok. I can do this as a workaround, at least I will get the "After Run" email. 


Any idea how to fix this?