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 reinstall the patch.

Alteryx Server Ideas

Share your Server product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Request the chained app timeout (chainedTimeout) be made a user-configurable parameter

See following article for background reference: https://community.alteryx.com/t5/Alteryx-Server-Discussions/workflow-exceeded-maximum-runtime-of-30-...


I have a support case (#00278355) advising unsupported changes to the alteryx.config file, involving an undocumented setting for chainedTimeout, as in:


<engine enableAutoLicensing="true" useServiceLayerComposer="true" chainedTimeout="10800"


This setting should be documented, supported, and made user-configurable through the System Settings GUI. 



10 - Fireball
I'm supporting this idea. I've recently come across this issue and had to dig through some KnowledgeBase articles and open a support ticket to figure out what was going on. The positive thing is it made me adjust my workflow through performance profiling.
Alteryx Community Team
Alteryx Community Team
Status changed to: Accepted



I'm updating this idea to the Accepted status, however I wanted to fully explain what that status would mean in the case of this idea. 


The ability to control the chained apps timeout through the System Settings would actually be controlled through the Designer product within Server, and thus by the Designer team. However the Designer team has not reviewed this idea, so I cannot provide insight if that's on the road map. However the underlying issue involving the chained apps timeout is being addressed by a large initiative involving our orchestration on Server.


Thus I'm moving this to Accepted as the source of the issue is being actively looked into. However if you would like this feature to be included on the System Setting, please feel free to post a corresponding idea on the Designer Idea board for the Designer team to review.