Upgrading Server to version 22.1? We’ve enabled the faster AMP engine by default. Read about how these system settings changes might affect you.

2022-05-24 Updates: Login: If you are facing issues with logging in, please try clearing all your cookies or trying another browser. We have a fix being deployed on the evening of 5/25. Email: If you're not seeing emails be delivered from the Community, please check your spam and mark the Community emails as not junk. Thank you for your patience.

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

Featured Ideas

Good Day.


We would like a built-in process that would search or, and resolve, workflows that are stuck in the "initializing" state. These seem to happen for various reasons but communication problems between the controller and workers .. usually a socket timeout.. which appears  to be most problematic. It seems  that these type of errors should be expected in all but the most stable environments,


Currently, the only tool that we have to solve this problem is to restart the Alteryx Service on the controller and while this works there tendency to cause some collateral damage in workflows ...erroring or restarting from their beginning.


There may be a way to solve this without restarting the service by editing Mongo using a tool like Robo 3T but that is unproven and has its own risk.


After dealing with this issue and struggling for quiet some time we think that the best option is to implement a "clean up" DB process that will run every 5 min or so, capture a list of workflows in the "initializing" state , then compare that list to one in the next 5 min cycle and fix any workflows that appear in both lists. We think that returning  any stuck workflows to the queued state would be the best Fix  option.


We just don't want to continue to use Restart the Service process to solve this issue and accept the collateral damage.


Thank you for your consideration


Tom D  





I would like to suggest the idea of being able to handle row-level security data sources in a more seamless way using Kerberos passthrough, where Alteryx Gallery will pass the information that User A is running the workflow to the underlying DB and will authenticate as User A. 


We have many workflows that are built to handle different queries of a database that are reliant on knowing who is running the workflow in Gallery. We also have many regional workers, and we want to keep the administration of these connections to the data as simple as possible. 


For more information, check out the Community thread on this subject.


For our large organization a requirement is that the Server connect to MongoDB cluster requiring keytab kerberos authentication. Can we please upgrade to needed MongoDB version that would support this as well as enable it within Alteryx Server.




As per design Alteryx Server retains all FAILED jobs in the Queue and Results collections even when we set the server to keep run history and results for x days


Purging records from Designer involves manual activity


Proposing the idea of purging these error records through automation script:


Step 1: Stop Alteryx Server

Step 2: Backup Mongo DB

Step 3: Replace big size files: AS_ResultsFiles.Files.bson, AS_Results.bson, AS_ResultsFiles.bson, AS_Queue.bson with Empty .bson files of same name in the backup/AlteryxService

Step 4: restore MongoDB from the backup (with the replaced files

Step 5: restart Alteryx service.


When I publish a workflow, I want it to have different behaviour based on the collection from which it was executed or scheduled. Let us suppose that I create a DEV collection and a PROD collection. The workflow is shared in both. If the workflow is executed from DEV, then I will have some logic to do X (output to specific folders, etc). If from PROD, the logic will do Y. The logic will be up to me. If the collection information is captured in the MongoDB layer, then I can pull it out on the fly by joining the collections, appInfos, and AS_Queue or AS_schedules collections. Querying the DB on the fly during execution and pulling that value is trivial. Once I have it, I can use it for any sort of logic as an environment sensing variable. Can you please store the info in MongoDB?


I would like to see ability to limit the number of versions a user can save of a workflow. As a server environment ages we start to see the database become unnecessarily larger because the number of version of workflows. For servers related to DEV and QA environments as an Admin I would like to be able to say users can keep their 10-25 most recent versions of their workflows. Then anything over that will start to auto-delete just like the auto save feature in Designer. 


Alteryx saves log files in UTF-16 please change the format to UTF-8 as the logs can be streamed using applications like New Relic to track the performance as they only support UTF-8 format.




We have a MongoDB connection string that we plug in to RuntimeSettings.xml during install.  Upon startup, the Mongo connection fails because RuntimeSettings.xml expects the connecting string to be encrypted.  The fix for this, is for someone to manually update the MongoDB connection via the Alteryx UI.  We would like a way to encrypt the MongoDB connection string for RuntimeSettings.xml before we start Alteryx for the first time.

Top Liked Authors