Server 2022.1 Release Notes

Last modified: November 21, 2022
Release Note Product Versions
Version Date Release End of Support
2022.1.1.25127 May 4, 2022 Major May 4, 2024
2022.1.1.30569* (Patch 1) June 15, 2022 Minor/Patch May 4, 2024
2022.1.1.30961 (Patch 1) June 23, 2022 Minor/Patch May 4, 2024

2022.1.1.40869 (Minor)

2022. (Patch 2)

September 8, 2022



May 4, 2024

2022.1.1.42590 (Minor)

2022. (Patch 3)

November 21, 2022 Minor/Patch May 4, 2024

*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 install the latest patch version. You don't need to uninstall 2022.1.1.30569.

Upgrade Considerations

As of version 22.1, there is a Designer compatibility limitation for environments with built-in authentication. To maintain compatibility with Server, download the latest version of Designer. 

Patch Updates

Alteryx now gives you the ability to patch your installation of Designer or Server without the need to perform a full uninstall and reinstall. You can download the latest patch from the Downloads & Licenses portal. For older patch versions, contact Fulfillment.

New Features

Removed Legacy OAuth1 Endpoints 

In preparation for a future FIPS-140 offering, we removed our legacy public OAuth1 API endpoints (they required SHA1 hashing which is not FIPS-compliant). This removal includes the legacy WCF (Windows Communication Framework) endpoints, Swagger for these legacy endpoints, and OAuth1 middleware. To replace the OAuth1 endpoints, you can use the OAuth2 versions of the legacy APIs released in 21.4. You have the same functionality with the OAuth2 APIs as you did with the OAuth1 APIs. The only exception is that the GET/workflows/id/package call now returns a file instead of a binary object in the response. 

We’ll continue to support subscription, V1, and V2 endpoints under OAuth2. 

To find out more about the conversion and its impact, visit the OAuth1 to OAuth2 Instructions help page or Conversion Instructions

AMP Engine Enabled by Default

We've enabled the AMP engine by default on Server so that new worker nodes can run workflows for both the original and AMP engines concurrently. We will be providing guidelines on how to manage memory with multiple concurrent jobs, and in different combinations of the original and AMP engines. For more information about AMP engine, visit the Engine and AMP Engine Best Practices help pages.

When you upgrade to Server version 22.1, we recommend validating your engine choice settings and resource allocations. The new 'Allow Server to manage workflows running simultaneously' functionality, and the change to enable AMP by default, can result in settings changing in your environment.

If you have an existing Server and want to maintain your current system settings, please read these instructions before upgrading.

1.    Controller > General > Enable AMP Engine 

      1.  Before upgrading, note your current settings.

      2. After upgrading, restore the selection to your desired value. 

2.    Worker > General > Allow Server to manage workflows running simultaneously 

      1. Before upgrading, note the number set for ‘workflows allowed to run simultaneously’.

       2. After upgrading, deselect ‘Allow Server to manage workflows running simultaneously’.

       3. Input the number you saved for ‘workflows allowed to run simultaneously’.

3.    Engine > General > Engine 

     1. Before upgrading, note your current settings.

     2. After upgrading, restore the selection to your desired value. 

4.    Engine > General > Run engine at a lower priority

      1. Before upgrading, note your current settings.

      2. After upgrading, restore the selection to your desired value. 

Required Password Reset for Built-In Authentication 

If you use built-in authentication, you need to reset your password due to improvements in security. If you do not reset your password in version 22.1, then you must have SMTP enabled to reset it in version 22.2. For more information how to reset your Server password after upgrade to 22.1, visit the Reset a User's Server Password help page. 

Along with the password reset, there is a Designer compatibility limitation for environments with built-in authentication. Older versions of Designer do not have the necessary password mechanism changes to authenticate with Server 22.1+. To ensure compatibility, you need to run Designer 22.1 or higher. 

Server UI Localization (Beta)

We’ve localized the Server user pages in 8 languages (English, Japanese, Chinese, Spanish, French, Italian, German, and Portuguese) and 90+ locales. This is a beta version because some content is still in progress. To update your language and local preferences, go to My Profile > General

Server UI Redesign

We’ve redesigned the Districts, Workflow Results, and Schedules user pages and the Collections, Credentials, Users, and Groups admin pages. The functionality of these pages remains the same. 

New Welcome Email to Users Created via a POST /users API Call

We created a welcome email for new users created via a POST /users API call. The new welcome email includes a link for the user to set their password. This user experience is similar to what new users see when their account is manually created. Note that the welcome email will be sent only if SMTP is configured.

Built-In Authentication Configuration Options for Login Attempts and Account Lockout

To prevent brute force attacks, we added a configuration setting called Number of Login Attempts Allowed, where an admin can set the number of attempts allowed before a user is locked out. We also added a setting called Account Lock Timeout (Minutes), which sets the time in minutes that a user will be locked out after they have reached the maximum number of failed attempts. The default is set to 5 login attempts, after which we lock out for 5 minutes. We also added a setting option that allows curators to decide whether they want to enforce a login attempt timeout or not. The administrator can update these 3 security settings under Server Configuration > Security Settings. These settings are only available when you use Built-In Authentication.

Go to Alteryx Server Configuration for more information.

Upgrade jQuery Utilized by the New Swagger 2.0 Documentation

We upgraded jQuery to its latest version, 3.6.0, for Server's API V3 Swagger documentation. This is part of a larger effort to remove old versions of jQuery. We expect to complete this later this year when we have redesigned the entire UI in the new React interface.

Migrated All Hashing Algorithms to SHA2 Using CryptoLib

In preparation for a future FIPS-compliant offering, we updated all non-Windows cryptographic calls in our codebase to rely upon a single Cryptographic Service Provider (CSP), the OpenSSL3-based module built and maintained by our DevSec team to FIPS-140 specification. This update should have no direct impact on user experience other than to make the solution more provably secure overall in its operation.

AES-256 Crypto Update

We migrated the cryptography we were using to secure legacy Data Connections (for example, DCM.E and API Secrets) to AES 256. This update has no direct impact on user experience, but it makes our solution more secure for our customers. 

Internet Explorer Not Supported

Internet Explorer will no longer be supported as of 2022.1. The supported browsers are Chrome, Firefox, Edge, and Safari. Go to Version Support Policy for more information.


Fixed and Known Issues



Major Release Version 2022.1.1.25127

ID Description Version Issue Status
Adding Data Connection fails if password has a pipe "|".  2022.1.1.25127 Fixed
When the AlteryxService instructs a worker to stop, the Alteryx Engine does not handle the user canceled message as an error. 2022.1.1.25127 Fixed
Base64 Encoder tool accepts a column of data but correctly encodes only every third record. 2022.1.1.25127 Fixed
Alteryx workflows flagged as "Error" while the Event message and logs indicate "Success".  2022.1.1.25127 Fixed
Schedules: Next Run timestamp is before the Last Run.  2022.1.1.25127 Fixed
Migrating schedules from Designer to Server invokes an error message. 2022.1.1.25127 Fixed
Rename option displays for non-owners of collection.  2022.1.1.25127 Fixed
Scheduler jobs have execution time 0.0 seconds.  2022.1.1.25127 Fixed

The Worker Configuration page in Server Configuration window has active input when the corresponding checkbox is deselected.

2022.1.1.25127 Fixed
When adding a renamed workflow to a collection, the old name displays in the Add Workflow dialog. After adding it to the Collection, the new name displays. 2022.1.1.25127 Fixed
TGAL-5831 Creation of user through Admin -> Users adds duplicate Studio in Subscriptions.  2022.1.1.25127 Fixed

Save button is not displayed when saving a workflow that is from other user's studio to Server.

2022.1.1.25127 Fixed
In the Admin panel > Jobs > Migrate tab, a user is not searchable if their role is set to Default, Viewer, or Member. 2022.1.1.25127 Fixed
TGAL-6009 Client version shows an invalid value in Server UI. 2022.1.1.25127 Fixed
TGAL-6039 Unable to change Collection Owner.  2022.1.1.25127 Fixed
TGAL-6042 User with admin access retains scheduling permissions until tab refresh. 2022.1.1.25127 Fixed
TGAL-6046 A negative number of the execution time showing in AS_Queue. 2022.1.1.25127 Fixed
TGAL-6080 Server API: POST & PUT /schedules use name instead of number for dayNumber.  2022.1.1.25127 Fixed
TGAL-6083 Able to create a Subscription with name containing only blank spaces. 2022.1.1.25127 Fixed
TGAL-6085 User searching does not work on middle-of-name text.  2022.1.1.25127 Fixed
Workflow version number is incorrect. 2022.1.1.25127 Fixed
Workflow Upload Date column in collections is labeled incorrectly.  2022.1.1.25127 Fixed
TGAL-6189 AlteryxService help documentation formatting is difficult to read. 2022.1.1.25127 Fixed
Error running workflows with DCMe shared connections for non-owner.  2022.1.1.25127 Fixed
Server API v3: POST /v3/usergroups/{id}/users unable to add users when using WinAuth authentication.  2022.1.1.25127 Fixed
TGAL-6251 Sorting Shared Source column causing loading issue on My Workspace page.  2022.1.1.25127 Fixed
Workflow can be published from a higher Designer version to a lower Server version and a scheduled job can run.  2022.1.1.25127 Fixed
Server API v1: Server API Endpoints GET /admin/v1/workflows and GET /admin/v1/workflows/jobs/ without a search filter do not return data.   2022.1.1.25127 Fixed
TGAL-6303 Server API v1: When using the /webapi/v1/workflows/{id}/package endpoint via the new API framework, the package download defaults to the wrong file extension. 2022.1.1.25127 Fixed
TGAL-6317 Server API v1: When using the v1 jobs APIs ported to the WebAPI, framework users in a WinAuth environment are unable to query the v1/jobs endpoints and return results.  2022.1.1.25127 Fixed
Using Private Subscription/Studio API keys with v1 Server API endpoints fails with an unknown exception. Endpoints in 21.4.1 are incorrectly recognizing Subscription/Studio keys. 2022.1.1.25127 Fixed
TGAL-6332 Server API v1: GET /v1/jobs/...{outputId} endpoint resulting in 500 response code.  2022.1.1.25127 Fixed
Schedules fail to load when database contains "Wrong" LastModifiedDate locale timestamp.  2022.1.1.25127 Fixed
DCMe: When sharing Data Source Connections with Custom Groups, any user within that Custom Group receives the error "Selected Connection is not available. Set one up to use the tool." after running the workflow. 2022.1.1.25127 Fixed
TGAL-6376 When creating a new user in the admin portal, 'Failed to create User.' message appears but the user is created. 2022.1.1.25127 Fixed
Server API V3: Creating schedules does not set the correct dates/times and recurring settings as desired. 2022.1.1.25127 Fixed
Artisan users are unable to run certain V1 endpoints via WebAPI when authenticating via Oauth2.  2022.1.1.25127 Fixed
Server API v3: Validation message still asking for revisionId instead of versionId when attempting to update existing workflow. 2022.1.1.25127 Fixed
TMEE-208 Server Admin Collections page gets broken after clicking on Insight link. 2022.1.1.25127 Fixed
TMEE-314 Collections > Workflows: Icons for workflows are poorly sized in dropdown when adding a workflow.  2022.1.1.25127 Fixed
Profile image file restriction does not match file type filter. 2022.1.1.25127 Fixed
Job history logs display message type ID instead of label.  2022.1.1.25127 Fixed
Chained apps on Server only run the first app in the chain.  2022.1.1.25127 Fixed
In WinAuth environments, the Public and Shared With Me tabs on the My Workspace page do not load when the owner of a public/shared workflow doesn't have a last name. 2022.1.1.25127 Fixed

Minor Release Version 2022.1.1.30569

ID Description Version Issue Status



After upgrading to 21.4, multi-line text is truncated and URLs are no longer visible on the Gallery page. 2022.1.1.30569 Fixed
2021.4: Date Picker Interface tool with no default value results in errors in the Server UI.  2022.1.1.30569 Fixed
TMEE-382 Banner Ads are no longer working in 21.4+. 2022.1.1.30569 Fixed
TMEE-383 Server: Hover text is not displayed while hovering over Banner Ad. 2022.1.1.30569 Fixed

Minor Release Version 2022.1.1.40869

ID Description Version Issue Status
TCPE-278 GCSE-465 Schedule shared in a Private Studio cannot be deleted by a non-owner. A 403 Forbidden error occurs from the backend, but no error is displayed in frontend unless the non-owner is a Curator. 2022.1.1.40869 Fixed


Alteryx Server API V3 Users endpoint: Attempt to create user fails. 2022.1.1.40869 Fixed
Alteryx Service does not start if the MongoDB is using the MMAPv1 storage engine.
When migrating to the latest version of MongoDB, the migration process will now convert your DB from MMAPv1 to WiredTiger in order to prevent compatibility issues that prevent the Alteryx Service from starting.
2022.1.1.40869 Fixed
Python-SDK tools using DCM run continuously on Server without completing or fail validation. 2022.1.1.40869 Fixed
TGAL-6733 Python tools with DCM.E enabled failed to run on the Server in 22.1 GA build (2022.1.1.38360).  2022.1.1.40869 Fixed
Few pages are not loading in User and Admin interface after applying the patch. 2022.1.1.40869 Fixed
TMEE-757 Workflow owners are unable to update the 'Ready To Be Migrated' flag via Workflow Settings. 2022.1.1.40869 Fixed

Patch/Minor Release Version 2022.1.1.42590

ID Description Version Issue Status
TGAL-6674 Addressed a page load performance issue due to excessive calls to a status endpoint. 2022.1.1.42590 Fixed



The POST /v3/workflows/{workflowId}/versions endpoint didn't work as intended. This was due to an inherent difference in how workflows are stored in Server when published via Designer versus how they are published via the API. As an interim step to prevent further issues with this endpoint we have temporarily disabled the endpoint and removed it from the documentation. We will reintroduce the endpoint once a solution is available that allows the endpoint to work in the intended manner. 2022.1.1.42590 Fixed



Intermittent issues with Server UI/Service after Professional Services upgrade. Customer is experiencing Server access issues with collections and other pages after upgrading to 2022.1. 2022.1.1.42590 Fixed
TGAL-6909 Corrected an issue where the installer wasn't recognizing the version of MongoDB properly during an upgrade if a patch had been applied to update MongoDB from 4.2.15 to 4.2.22. This caused the installer to incorrectly report an error indicating the user was attempting to upgrade from an unsupported version of MongoDB. 2022.1.1.42590 Fixed


App Re-Run: Analytic App questions are reset to the defaults instead of retaining the values that were entered. 2022.1.1.42590 Fixed



Major Release Version 2022.1.1.25127

ID Description Version Issue Status
When you save a new version of a workflow with an existing schedule, the updated workflow version does not show on the schedule.  2022.1.1.25127 Known
Users are not shown in Add User dropdown of Data Connections when username is in Japanese characters - this issue is  Lucene related.  2022.1.1.25127 Known
TGAL-6307 WebAPI: Get Package API v1 corrupts YXZP files when using the interactive documentation (Swagger).  2022.1.1.25127 Known
TGAL-6338 Some IDP login forms do not render correctly in Alteryx Configuration.  2022.1.1.25127 Known
DST (Daylight Savings Time) alters future interval scheduling of jobs/workflows.  2022.1.1.25127 Known
TGAL-6401 The emailed link to confirm an email address directs you to an error stating the user has already been validated.  2022.1.1.25127 Known
Assigning default worker tag to subscriptions does not function properly. 2022.1.1.25127 Known
Canonical name has no bearing on Notification URLs.  2022.1.1.25127 Known
Permissions change fails with error when configuring user with null Last Name. 2022.1.1.25127 Known
POST /v3/workflows/{workflowId}/versions does not show in UI for workflows uploaded from Designer.  2022.1.1.25127 Known
Unable to Peform Date Filtering via v3/schedules Gallery API Endpoint.  2022.1.1.25127 Known
Alteryx Server API V3 Users endpoint: Attempt to create user fails.  2022.1.1.25127 Known
TGAL-6482 DELETE v3 for /users/ fails if there's a workflow in the Public space.  2022.1.1.25127 Known
PUT /users/ v3 fails if user has a null lastName.  2022.1.1.25127 Known
Need to check historic claims attributes before checking alternates.  2022.1.1.25127 Known
TMEE-382 Banner Ads are no longer working in 21.4+.  2022.1.1.25127 Known
TMEE-383 Server: Hover text is not displayed while hovering over Banner Ad.  2022.1.1.25127 Known

Security Updates


Major Release Version 2022.1.1.25127

ID Description Version Issue Status

SV: Fixed a potential Directory Traversal weakness which could have allowed limited filesystem reconnaissance of the Server’s folder structure.

2022.1.1.25127 Fixed
SV: Removed unused ‘Password2’ field from plaintext response.  2022.1.1.25127 Fixed


Minor Release Version 2022.1.1.40869

ID Description Version Issue Status

To be disclosed.*

All 2022.x versions Known



To be disclosed.* All 2022.x versions Known

*In accordance with security best practices and to prevent potential manipulation by bad actors, Alteryx does not disclose the details of any open vulnerability until all supported versions are updated with a fix. Beginning with 2022.3, releases and updates will become available and will continue until the fix has been supplied for all supported versions. To ensure that all versions you use are promptly fixed, regular updates are strongly recommended. More information will be made available once the vulnerability has been fixed for all supported versions that were impacted.



Patch/Minor Release Version 2022.1.1.42590

ID Description Version Issue Status
TDS-555 SV: Update OpenSSL to 3.0.7; remediates CVE-2022-3602 and CVE-2022-3786. 2022.1.1.42590 Fixed

To be disclosed. *

2022.1.1.42590 Fixed
SV: The embedded MongoDB in Alteryx Server < 22.3 contains a known Denial-of-Service vulnerability (CVE-2021-32036); the exploit requires authenticated user access to the MongoDB installation, which is not something Alteryx Server provides by default but which many customers have enabled for direct monitoring of their Server's database backend.  2022.1.1.42590 Fixed

*In accordance with security best practices and to prevent potential manipulation by bad actors, Alteryx does not disclose the details of any open vulnerability until all supported versions are updated with a fix. More information will be made available once the vulnerability has been fixed for all supported versions known to be affected. 

Was This Page Helpful?

Running into problems or issues with your Alteryx product? Visit the Alteryx Community or contact support. Can't submit this form? Email us.