Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHello all,
This may be a little controversial. As of today, when you buy an Alteryx Server, the basic package covers up to 4 cores :
https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/How-Alteryx-defines-cores-for-licensing-our-products/ta-p/158030
I have always known that. But these last years, the technology, the world has evolved. Especially the number of cores in a server. As an example, AMD Epyc CPU for server begin at 8 cores :
https://www.amd.com/en/processors/epyc-7002-series
So the idea is to update the number of cores in initial package for 8 or even 16 cores. It would :
-make Alteryx more competitive
-cost only very few money
-end some user frustration
Moreover, Alteryx Server Additional Capacity license should be 4 cores.
Best regards,
Simon
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.
Sorry if this idea has already been addressed, but I would love an enhancement that would allow users to upload multiple files to the Gallery to be processed and ran by a published app.
Currently, the only way to accomplish this is by adding multiple File Browse tools to the published app. But if you have a workflow that needs to upload more than a couple files, this becomes a problem.
Similar to other code/software repository, it would be nice to have the ability to add a message to the reason why a workflow is updated/modified for users of a collection with access can easily review and revert back to older versions quickly.
Fix typo in introduction to user guide
Hello Alteryx Team,
I hope this message finds you well.
I would like to propose a utility enhancement for Alteryx Server, particularly at the enterprise level. It would be extremely beneficial to have a workflow-based utility that can be configured for any licensed environment to perform scheduled backups and similarly facilitate the restore process.
Currently, the restore process is quite tedious and heavily reliant on the Server Host Recovery Guide. Post-recovery, we often encounter multiple errors, especially related to connections and add-ons, which makes real-time disaster recovery (DR) environments difficult to manage and unreliable.
While PowerShell scripts can be developed to assist with recovery, they still require significant manual intervention and troubleshooting. A built-in utility would greatly simplify the administrator's job and improve the robustness of DR strategies.
I kindly request the Alteryx internal development team to consider this feature request. I also encourage community admins and users to vote for this suggestion so it can gain visibility and traction.
Best regards,
Sheik Sabir Ali, G
Our organization heavily leverages Active Directory for all data connections. We manage access to Alteryx Gallery Collections by Active Directory. If I want to use DCM, and share the connection, I can only specify an individual or a custom group of individuals. This is against our efforts to manage security and access usingDCM Active Directory. It would be incredibly beneficial for Alteryx DCM to support connection sharing using Active Directory. Another alternative would be to allow active directory groups to be added to custom user groups.
TLS certificate lifespans will be changing starting in 2026. Managing certificates manually will become a headache for many Alteryx Server administrators. Create a method to allow automated TLS certificate installation in Alteryx Server.
47-day SSL/TLS certificates will be the new standard in 2029
The newly approved measure, initially proposed by Apple and endorsed by Sectigo in January 2025, will gradually reduce certificate lifespans from the current 398 days to 47 days through a phased approach.
Ballot SC-081v3 formally passed on April 11th, 2025, putting the phased reduction into effect with the following enforcement dates:
March 15, 2026: Maximum certificate lifespan reduced to 200 days
March 15, 2027: Further reduction to 100 days
March 15, 2029: Final enforcement of the 47-day maximum lifespan
For admins to be able to prioritize workflows, because by default, users are not allowed to prioritize jobs.
In combination with Quality of Service (3 - Critical Priority and above) and worker tagging, for example we have all workflows belonging to a project tagged to a specific worker, but since "Member" (default) users cannot prioritize jobs, these workflows would never run on this specific worker
Automatic Deletion of Logs files from Engine, Service and Gallery Folders for on perm servers
I think file explorer or management related to workflow in the server should be able to be seen, linked and reffered to so that much more creative way to check and use them in the server via multiple workflow can be realized.
There are some products in the Market whic allows to install multiple services as Windows service on a single server.
In large organizations it is found that when we are running ALteryx Server in multi node setup at that time 1 worker server has only one Alteryx service installed and runs as single windows service. If we have configured FID with log on as a service FID in that case if one FID reached to its shared path mapping capacity 1018k then it stops authentication and windows service is not able to start.
If we have multiple services installed on the same server then we can configure like :
AlteryxService.exe : FID1
AlteryxService2.exe : FID2
AlteryxService3.exe : FID3
In this case we can utilize the server compute and enhance the multi tenancy instead of adding more additional server.
The gallery needs to implement basic auditing in the data connections.Currently, there is no way to determine who or when a data connection was created or updated.
The dataConnections Collection contains data connections with these keys
_id: (ObjectId) Document primary key.
ConectionString: (String) Hashed database connection string.
PasswordSecured: (String) Encrypted password for the database connection.
ConnectionName: (String) Data connection display name.
Subscriptions: (Array) Array of subscription IDs the data connection has been shared with.
Users: (Array) Array of user IDs the data connection has been shared with.
UserGroups: (Array) Array of group IDs the data connection has been shared with.
Add these keys to provide a basic audit trail
Modify the gallery to allow the values of the new keys to be displayed. Modify the API endpoint to retrieve this information.
You cannot currently upload a new workflow and specify your own workflow_id GUID. This would be useful for systematic workflows that need to be referenced in code. Currently, you either to search for a workflow by name, but you are not guaranteed it a workflow instance you uploaded. This would be helpful for server and workflow administration.
Given there are multiple api versions. I need a way to call the api and get the server version so I can make the correct API call or construct code logic which provides the user code requirement based on the versions features or limitations.
I propose a api call ../getserverinfo/ that returns server metadata like version, default worker thread count, and default memory allocation.
There is currently not a way to call the API and find out the calling user. For instance, if I have a user API key and secret, I to return the rest of the user info for the calling user or who is calling the api. I propose a api call like ../user/whoami
I would like to be able to suspend scheduled jobs - those that are queued to run.
The only option currently is just to delete them.
I want to be able to 'put them on hold' then release them as and when is convenient. Once you release them, they just go back in to the queue or run if there is a free scheduling slot.
In one fell swoop, you can see if all the workflows included in the collection have run smoothly.
I did it with a workflow but it should be native.
When using a flow that produces multiple outputs each has to be selected in turn and downloaded, which is no effecient.
It would be a better user experience if standard selection box functionality where the user can select one or multiple files they wish to download, including a box to select all and where more than a singular file is chosen they are provided as a singular zipped download.
the idea would be to be able to chain Workflows (execute Workflow B at the end of Workflow A). Or to condition the execution of a Workflow in relation to another when there are dependencies.