Featured Ideas
Hello 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
In the View Schedules screen, currently one must select the Controller at the beginning of each session before being able to see any workflows, schedules, queue or results. This is especially annoying when a company only has one controller and yet must select it each time. However, I would guess that even when an organization has multiple Controllers, each individual user is likely to spend most of their time in one.
It would help both of these situations if the most recently used controller is automatically selected when launching Alteryx Designer.
As part of the Persistence Expiration processes, within Designer we have the ability to set a retention threshold of the results tab. i.e. 30 days.
After enabling this - all completed results are purged but all the "error" results remain. And this depending on the original count can run into the thousands, such as in my environment. Id like to see the "Error" results become part of the clean up processing because of the following reasons:
1. We do not have dedicated admins that have time to manually or by group delete these error result items.
2. Most if not all - errors are resolved immediately. if there were to be kept as a reference, a screen shot of the results are normally taken and filed away.
Support says this is intentional for resolution tracking purposes - but to counter - as I stated in item 2 - most errors are immediately looked at and worked on. So there is no reason to keep errored results. Especially when they are time-stamped dates greater than the expiration values selected.
Currently only 5 workflows are displayed per page in a collection. Currently we have about 30 workflows (soon to be about 100) and paging through workflows to find the one you want to run is time consuming.
It would be great if there was an option on the page so the user could select the number of workflows per page.
If you are viewing schedules, on the Queue Panel, you should have the option to refresh the information to get an idea how far things are progressing. If you swipe back and forth between panels you get updated % done information, so it is definitely available. Not the most pressing need, but a very easy fix.
Ninja Edit: Did not know there was a dedicated server ideas forum so I removed a part.
When you want to re-run a chained app in Alteryx Server, give the option to run the first, second, etc app. Right now it only reruns the last app.
I am running version x of Alteryx locally and my server is running x-2. If I publish a workflow with error reporting via email, the server is not able to recognize that my workflow has error logging because it automatically kicks a version error. The events portion of the XML should be read regardless of the server version and trigger an error when this happens.
Hi All,
We are preparing to rollout Alteryx Server in a large organisation and can see that the creation of Collections by many analysts may become problematic over time.
It would be good if we can disable the functionality and only allow for gallery admins to create new collections.
Cheers
Fi
(Commonwealth Bank of Australia)
It is more convenience that allowing gallery admin to download any workflow from the gallery for trobleshooting.
For example, if the workflow is long running , the gallery admin can download the workflow and then drill down to it to find out the root cause. Sometimes, it maybe workflow design related issue.
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.
I did not find a better category, but this issue relates to Data Connection Manager and credential setup with key files in a Server and Desktop environment.
Issue: When using key file credentials in DCM a Key File Path needs to be specified. This path cannot be a UNC or Mapped drive, has to be a local drive for Google BigQuery with the latest Simba ODBC driver at least. This prevents centralized credentials management and defeats the purpose of DCM. I understand this might be a driver limitation, however it's still an issue that I think Alteryx could handle.
Suggestion: Since the key file is simple text (JSON) file, it could be embedded (i.e. uploaded via the DCM interface) into the connection itself. That way it can be centrally distributed to the local computers when the DCM connections are synchronized from the server (or vica versa). I would also store them encoded for Information security reasons.
Bonus: Tying into this it would be really good if Alteryx Desktop would automatically sync Server DCM connections when a connection is made to Alteryx server the first time after the software was launched (i.e. opening a Server workflow) to keep it automatically updated.
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
My gallery have more than 100+ notifications. it hard to click one by one.
Want to have mark all as read button for this.
if possible split message to 2 type, admin and system, where:
1. admin (for communication)
2. system (grant user access, share workflow and etc.)
During a recent project, I explored the Alteryx Server Download a Workflow Package API Endpoint, which includes an optional versionId parameter. The documentation suggests that this parameter should allow users to retrieve specific, prior versions of a workflow package by supplying the appropriate version ID. However, in practice, I found that regardless of which valid prior version ID was provided, the API always returned the current published version of the workflow.
This behavior presented a challenge for our automation use case, where we aimed to implement version control and retrieval solely through Alteryx Server, rather than relying on external tools like Git. After thorough testing and validation, I shared these findings with Zach Hamilton and Marty Moravec at Inspire 2025, who were able to confirm the behavior.
I appreciate the continued enhancements and support the Alteryx team provides for the Server platform and its APIs. Resolving this issue would greatly benefit users who depend on robust version management and automation capabilities within Alteryx Server. Thank you for considering this feedback, and I look forward to future improvements in this area.
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
Please bring back the feature for showing the approximate file size for a workflow & dependencies when publishing/saving to the Gallery. This "feature" was part of 9.5 (see lower left in the attached screenshot). This is a useful indicator and helps highlight when there is a large external dependency that will get replicated onto the server when publishing.
An example of when this is useful:
When a publisher sees a large file size, they might change the dependency path from being a local path (that will result in a copy being published to the server) to a UNC path i.e. \\servername\path
It might also be useful to add the size information as a column in the "list view" in the Gallery.
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.
As the Alteryx Server administrator, I would like to see this functionally restored.
See attachment
The current Enterprise Utility Workflow does not have a match/look-up in place between the two environments for user ID's. Thus, the migration workflow doesn't work without adding in a couple extra API calls. When we upgrade to a new version of the utility, I have to add this back in.
It would be nice if the workflow would come with this already configured.
