Server 2024.1 Release Notes
Release Note Product Versions | |||
|---|---|---|---|
Version | Release Date | Release | End of Support |
2024.1.1.17 | May 1, 2024 | Major | May 1, 2026 |
2024.1.1.49 (Minor) 2024.1.1.1.49 (Patch 1)* | May 23, 2024 | Minor/Patch | May 1, 2026 |
2024.1.1.71 (Minor) 2024.1.1.2.71 (Patch 2) | June 27, 2024 | Minor/Patch | May 1, 2026 |
2024.1.1.93 (Minor) 2024.1.1.3.93 (Patch 3) | July 25, 2024 | Minor/Patch | May 1, 2026 |
2024.1.1.136 (Minor) 2024.1.1.4.136 (Patch 4) | September 5, 2024 | Minor/Patch | May 1, 2026 |
2024.1.1.168 (Minor) 2024.1.1.5.168 (Patch 5) | November 21, 2024 | Minor/Patch | May 1, 2026 |
*This patch release affects both the GA and FIPS versions.
Upgrade Considerations
Warning
This section contains important updates regarding the 2024.1 release. Please review these items before you upgrade.
Python Version Upgrade
We have upgraded the embedded Python version to 3.10.13. Go to Alteryx Embedded Python to review important up-to-date information and resources.
Please note that there are important compatibility considerations with regard to Alteryx-built Python tools. Go to Alteryx Connectors for 24.1 to learn how to implement versions that are compatible with Designer and Server 24.1. These tools include Data Connectors (formerly available on Community, now available on the Alteryx Marketplace), Alteryx Intelligence Suite tools, and Enterprise Utility tools.
Insights End of Life
With the 2024.1 release, the Insight tool* has reached end-of-life and is no longer available in Alteryx Server. In Designer, the tool has been deprecated, however, if you still need to access the tool, right-click the Designer tool palette and select Show Deprecated Tools.
Please also note that the Insight tool's Preview functionality is no longer available in Designer due to compatibility issues with the Alteryx upgrade to Python v3.10. You can continue to view your data and design via the Design tab of the Insights tool.
To understand how this might impact you, please visit our FAQ page.
*This note is specific to the Insight tool and not the Business Insights Data Product.
Studios (Subscriptions) Retained
We're pleased to inform you that we are no longer deprecating Studios and will continue to maintain it in all supported versions. We still recommend you to use Collections for the best asset sharing experience.
Alteryx Server-FIPS
Alteryx Server version 2024.1 offers separate GA and FIPS 140-2 capable products. Please note that these standards are developed by the US National Institute of Standards and Technology (NIST) for use by US government agencies and contractors. For more information about FIPS, go to the NIST FIPS FAQ page.
The general (non-FIPS) release version of Alteryx Server is not capable of FIPS operation. A separate release (and installer) is available under separate license terms for our FIPS 140-2 customers. Contact your Alteryx Sales Representative for more details.
Feature Differences
Server-FIPS 2024.1 has a few features that are not available or limited in function when compared to the non-FIPS Server releases. See Alteryx Server and Server-FIPS Feature Differences for reference.
New Features
Transfer Asset Ownership
In this release, we've provided admins with the option to transfer ownership of workflows and schedules between users without them needing to be in the same studio as the new owner. This will make it easier to manage workflow and schedule ownership, especially when employees leave the company. This will improve collaboration and prevent tedious rework when workflow owners change, avoiding data pipeline disruptions.
For workflows, this means that when the workflow is transferred to a new owner, the workflow will move from the old user’s studio to the new user’s studio and the ownership field will be updated. When workflows are transferred, the version history will remain which is essential for audit compliance and version control.
Along with this new functionality, new notification options are available in Notifications. These are automatically on when you upgrade. Notifications are sent when you transfer workflows via both the Server UI and API. Both past and new owners are notified. For more information, go to the Notifications help page.
You can transfer asset ownership in Server UI or using Server API V3 endpoints.
Transfer Asset Ownership in Server UI
Admins are now able to transfer asset ownership from the Server UI for individual schedules or workflows, as well as in bulk. The bulk transfer of assets enables smoother transitions, without heavy reliance on APIs.
For more information about this feature, go to Transfer Workflow Ownership and Transfer Schedule Ownership.
Transfer Asset Ownership Using Server API V3
We now allow admins to transfer ownership of workflows, schedules, and collections between users using our V3 APIs without needing them to be in the same studio as the new owner.
PUT /v3/workflows/{workflowId}/transfer
This new API call adds the ability to transfer workflow ownership of a single workflow regardless of a studio. Thus, an admin can transfer a workflow to a user who isn’t in the same studio as the workflow.
There’s an additional option to transfer all schedules related to that workflow that the current workflow owner owns. This allows admins to transfer a workflow and the schedules associated with it at the same time. The schedules that are transferred will only be the ones owned by the existing workflow owner.
PUT /v3/users/{userId}/assetTransfer
This new API call allows admins to transfer all workflows, schedules, and collections from one user to another in a single call. The admin can choose which of these assets to transfer. This allows admins to quickly and easily transfer all assets from one user to another.
These APIs will make it easier for customers to manage workflow, schedule, and collection ownership. For more information about the new API endpoints, go to Workflow Endpoints and User Endpoints.
SQL Database Support
We’ve added support for SQL user-managed instances alongside the existing MongoDB integration. This addition provides you with the flexibility to leverage relational databases according to your preferences and requirements. We included the SQL DB support feature in both FIPS-compliant and non-FIPS environments. At the moment, we support only Microsoft SQL Server.
To start using SQL DB with your Alteryx Server, you need to configure it in Alteryx System Settings.
Controller:
In Controller > Persistence, we’ve added the User-managed SQL DB option which allows you to connect to your SQL DB.
In Controller > Persistence> Database > SQL Connection, enter the SQL DB connection string.
For more information on how to configure your controller with SQL DB option, go to Controller.
Server UI:
In Server UI > Persistence > Advanced Connections, the Server Persistence UI is automatically populated for the Advanced SQL Connection if you have selected User-Managed SQL DB in the Controller > Persistence section.
In Server UI > Persistence > Web Persistence, enter the SQL DB connection string. A MultipleActiveResultSets (MARS) flag will be automatically added. Alteryx Server needs this flag to perform complex querying. Without this flag, several operations would not be possible and Server would not be fully functional. For more information on this flag, please visit Multiple Active Result Sets (MARS).
For more information on how to configure Server UI with SQL DB option, go to Server UI.
For more information on how to manage SQL DB in Server, visit the SQL DB Management help page. Under this page, you'll find more details about SQL DB schemas, connection strings, and Mongo to SQL Migration Guide. For a general overview of our SQL support and migration from MongoDB to SQL, visit Server SQL DB Customer FAQ.
Crypto Migration Improvements
We've made the following improvements to the crypto migration process:
Migration Prep Tool Improvements
To evaluate any anticipated issues you might need to address prior to upgrading to 2022.3 or later, run a pre-flight check with the Migration Prep Tool.
During the pre-migration or full migration process, you will be able to see improved error logs that allow you to resolve the issues yourself. This enables you to take recommended action to ensure the full migration is completed successfully despite any errors.
We have added 3 new run options when running the Migration Prep Tool:
Default: Run the pre-migration and pre-migration check simultaneously (-p)
Run just the pre-migration (apps) (--appsonly)
Run just the credential validation step (--credonly)
While running the Migration Prep Tool, you must provide the controller token (-t) and hostname/IP Address (-i) of the controller. This also means you can now run the Migration Prep Tool on a multi-node setup by providing the controller's hostname/IP address and controller token.
Please note that 2 instances of the Migration Prep Tool tool cannot run simultaneously for the same controller.
Improved Error Messages
Example of an improved error message:
2024-02-28 10:06:38.038910;3;Error parsing xml file 'C:\ProgramData\Alteryx\RuntimeSettings.xml': char position=0; Message=File was not found
2024-02-28 10:06:38.038834;3;<Error parsing xml file 'C:\ProgramData\Alteryx\RuntimeSettings.xml': char position=0; Message=File was not found>. Please verify <"C:\ProgramData\Alteryx\RuntimeSettings.xml"> exists.
For more information about the pre-flight check, go to Run the Migration Prep Tool.
UI Search and Sort for Workflows and Schedules
We have improved our searching and sorting capabilities on Server for both admin and non-admin users, enhancing the overall experience of the Server UI. Now you can do the following with ease:
Search by 'Workflow ID' on Schedules and My Workspace (tabs My Files, Shared With Me, and Public).
Search by 'Owner' on Schedules and My Workspace (tabs Shared With Me and Public).
Filter by engine ‘AMP’ on Schedules and My Workspace (tabs My Files, Shared With Me, and Public).
Filter by ‘Type’ on My Workspace (tabs My Files, Shared With Me, and Public).
For more information on search, go to Search for Assets.
Server SAML Authentication Without Using CEF
We changed Designer's SAML authentication browser from Chromium Embedded Framework (CEF) to the machine's default browser. This will help you avoid security issues with CEF becoming out of date before Designer can be released with an updated version.
Service Timestamps Moved to UTC Format
All timestamps in the Server databases have been converted to the UTC format. By default, in the user interface now all the date-time fields will be displayed as per user’s profile time zone. The only exception is the frequency field, where it shows the timezone that is chosen at the time of creating the schedule.
If you are taking timestamps directly from the Server database, please note that these timestamps have been migrated to UTC format for standardization across the product and to alleviate daylight saving time issues.
Affected APIs
All Server APIs with a timestamp element will now return date and time fields in UTC-0 timezone.
The list of affected APIs via Swagger includes:
POST /v3/schedulesPUT /v3/schedules/{scheduleId}GET /v3/schedulesGET /v3/schedules/{scheduleId}
For more information about these API endpoints, visit the Schedules Endpoints help page.
In case you upgrade from an older version to 2024.1, the timestamps of existing assets will be converted to the new UTC standard when AlteryxService starts.
Note that AlteryxService uses third party libraries to keep the updated time zone information in the database. These need to be updated as and when there is an update. If there is a time zone which is not providing correct offset values, please wait for the library update.
DCM Environment Connection Handling
We’re introducing DCM Environment Connection Handling allowing you to define what connections present on the Server should be used instead of workflow connections when executing workflows on the Server. This feature is available to all Curators through the Server UI and via Server APIs.
For every environment, you can define a list of Connection IDs that should be replaced by a different connection when found in workflow during execution. In other words, for such an environment, each of the source Connection IDs (present in the workflow) will be resolved as the target connection (defined by Connection ID) at engine runtime. That means a single workflow can be executed differently (using different connections) on each Server without making changes to the workflow itself. DCM handles connection replacement dynamically at the execution, without updating the YXMD workflow.
In a single-Server setup, you can still make sure that the workflow is executed differently in the Designer than on the Server. This enables an easier lifecycle of workflows across multiple environments (dev, test, production) without making changes to it.
For more information about DCM Environment Connection Handling rules, go to DCM Connections and DCM Connection Handling. To review permissions needed for DCM Environment Connection Handling rules, go to User Roles and Permissions.
To check the API endpoints to manage DCM Environment Connection Handling rules, go to the DCME Endpoints help page.
DCM Generic External Vault
You can utilize the DCM configuration to fetch secrets used in DCM credentials at runtime from a vault by providing a custom script or executable that would handle authentication and secret retrieval. Forming such a vault is possible through Designer and Server.
Generic External Vault allows you to configure a generic vault that can retrieve secrets from any vault with a programmatic interface using basic authentication.
For more information, go to DCM - Server, Data Connection Manager: Server UI, and DCM Generic External Vault.
DCM Permissions
Along with other new DCM features and changes, we’ve added new DCM permissions, giving Server Curators better control over users' DCM connections present on the Server.
Create or Edit DCM Assets
Share DCM Connection Credentials to Run on Server Only
Share DCM Connection Credentials for Collaboration
Manage Generic Vaults
These permissions are automatically enabled for new and existing users, except for the Manage Generic Vaults permission.
For more information, go to the User Roles and Permissions help page.
DCM Concurrent Sharing
Now you can share the same connection with one user for collaboration, and with another user or with the same one for execution. For more information go to Data Connection Manager: Server UI.
HashiCorp Vault mTLS Authentication
There is a new authentication method for HashiCorp Vault. Server can now use mTLS (“mutual TLS”, also known as “TLS Client Authentication”) to obtain DCM secrets from Vault.
Fixed and Known Issues
Fixed Issues
Fixed Major Release Version 2024.1.1.17 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-672 GCSE-1329 | After installing Server on the Japanese, Chinese, or French operating system environment, Server UI doesn't open and the message "HTTP 500 internal server error" is displayed. | 2024.1.1.17 | Fixed |
TCPE-772 GCSE-1545 | The PUT /v3/schedules/{id} endpoint changes HOURLY frequency to ONCE. | 2024.1.1.17 | Fixed |
TCPE-841 GCSE-1685 | In Server UI > Admin > Settings > Configuration > Users, the Users Can Register setting can be unchecked with Active Directory Authentication in 2022.3 and 2023.1. | 2024.1.1.17 | Fixed |
TCPE-853 GCSE-1754 | The customer Web application proxy is showing a 400 Bad request when a POST API call is made to aas/sessions. The content-type: application/json with “POST” is flagged as invalid JSON. | 2024.1.1.17 | Fixed |
TCPE-868 GCSE-1741 | When reindexing 2023.1 Server, a 500 error occurs, indicating that the reindex failed. Users can't see their workflows but can see the workflows shared with them. | 2024.1.1.17 | Fixed |
TCPE-893 GCSE-1853 | Indexing fails on upgrade or reindexing on Subscriptions collection when a Name field is NULL. This results in the index not being built and the Admin > Subscriptions page appearing blank without any error message. | 2024.1.1.17 | Fixed |
TCPE-921 GCSE-1888 | The POST /admin/v1/workflows endpoint is returning "An item with the same key has already been added." exception message for specific YXZP files. | 2024.1.1.17 | Fixed |
TCPE-935 GCSE-1909 | Server Data Connections become corrupt and appear as encrypted values when custom groups assigned to the connection are deleted from Users > Groups page. | 2024.1.1.17 | Fixed |
TCPE-940 GCSE-1916 | After upgrade to Server 2022.3+ with SAML authentication, the ACS endpoint is exposed as lowercase (/saml2/acs) compared to uppercase (/Saml2/Acs). This causes issues during login and startup. | 2024.1.1.17 | Fixed |
TCPE-952 GCSE-1926 | Upgrade MongoDB Database tools version to v100.7.0 for Mongo 4.2 and 4.4: MongoDB restores fail with some frequency by overloading memory. | 2024.1.1.17 | Fixed |
TCPE-955 GCSE-1925 | AlteryxService.exe emongodump/emongorestore does not return a Mongo restore error to the customer. Instead returns a false success message. | 2024.1.1.17 | Fixed |
TCPE-957 GCSE-1936 | Performance issue with the DELETE /v3/workflows/{workflowId} endpoint. If the database has only a few thousand schedules, this results in an unreasonable amount of time to perform even for workflows without set schedules. | 2024.1.1.17 | Fixed |
TCPE-973 GCSE-1951 | The GET /admin/v1/workflows endpoint does not return all workflows. It returns only first 15 and won't return more than 1000. | 2024.1.1.17 | Fixed |
TCPE-981 GCSE-1934 | The POST /v3/workflows API works incorrectly. If a workflow or app has dependencies that are located in the same folder when packaged, the API takes the file type of the first dependency listed alphabetically. | 2024.1.1.17 | Fixed |
TCPE-1010 GCSE-1873 | Schedules are running an hour earlier than the scheduled time. | 2024.1.1.17 | Fixed |
TCPE-1020 GCSE-2005 | Analytic App on Server is not passing value when Annotation Name has a period 23.1/23.2. | 2024.1.1.17 | Fixed |
TCPE-1026 GCSE-2017 | Workflow comments added via Designer are not being returned by the /v3/workflows/{workflowId} endpoint. | 2024.1.1.17 | Fixed |
TCPE-1029 GCSE-2027 | The GET /v1/workflows/subscription API endpoint is not returning all workflows. When no limit parameter is specified, only the first 15 workflows are returned. When the limit parameter is used and set to a value > 1000, only the first 1000 workflows are returned. | 2024.1.1.17 | Fixed |
TCPE-1100 GCSE-2185 | After the upgrade, all workflows show a revision number of 1. This was addressed as part of TGAL-7199. If you continue to see incorrect revision numbers, please contact customer support for a manual fix. | 2024.1.1.17 | Fixed |
TCPE-1105 GCSE-2204 | MongoDB: Duplicate key error collection - AlteryxGallery.locks keep generating in Mongo versions 5.0 - 6.0. This behavior is not an Alteryx defect, and no changes were made to our software. | 2024.1.1.17 | Fixed |
TGAL-6394 GS-610 | Daylight Saving Time (DST) alters future interval scheduling of jobs/workflows. They are being pushed to the top of the hour when scheduled during the DST window of 2AM - 2:59AM. For more information about the DST change, visit Schedules: Time Zone Support. | 2024.1.1.17 | Fixed |
TGAL-6467 GCSE-464 | Daylight Saving Time (DST) is causing schedules to run at incorrect time in Server - schedules are shifted an hour forward or backward during the Daylight Saving Time. For more information about the DST change, visit Schedules: Time Zone Support. | 2024.1.1.17 | Fixed |
TGAL-7406 GCSE-1123 | The frequency column in the schedules table is showing the wrong dates for recurring schedules when the schedule’s time and timezone and the equivalent time in the user profile’s timezone span different days. | 2024.1.1.17 | Fixed |
TGAL-8184 TCPE-740 | Certain CredentialPasswordID values are causing MongoDB migration to schema 42 to fail and preventing successful upgrade to 2022.3+. | 2024.1.1.17 | Fixed |
TGAL-8378 GCSE-1511 | Server 'Version' on the My Profile page is not properly displaying Patch versions. | 2024.1.1.17 | Fixed |
TGAL-8625 | Even when given wrong version ID ,Workflow package is downloading through the | 2024.1.1.17 | Fixed |
TGAL-8733 GCSE-1694 | Index rebuild process fails in 2023.1 when Server data connection ConnectionString character length exceeds MongoDB index key limit of 1024 bytes returning an error "Index key too large to index" and causes Users/Subscriptions page to be blank. | 2024.1.1.17 | Fixed |
TGAL-9017 | Error: "Failed to retrieve Mongo connection information <Server Error: 404> after Installing Alteryx Server 2023.2 with User-Managed MongoDB. If your Server environment has user-managed Mongo DB on isolated Server nodes that use advanced connection strings to connect to Mongo DB, you must edit the runtimesettings.xml file, or else the service will not start. Please follow the workaround instructions in this article. | 2024.1.1.17 | Fixed |
TGAL-9100 GCSE-1839 | DCM and Server Data Connection issues after host migration and upgrade to 2023.2. | 2024.1.1.17 | Fixed |
TGAL-9126 GCSE-1852 | Server Reindex API endpoint | 2024.1.1.17 | Fixed |
TGAL-9254 GCSE-1869 | Designer is able to save workflows to Server when Designer version is higher than Server. | 2024.1.1.17 | Fixed |
TGAL-9302 TCPE-923 | Server UI Data Connections are not syncing to Designer post upgrade. | 2024.1.1.17 | Fixed |
TGAL-9658 | Unable to upload Journal app workflow shared by RSM client with SQL as database and Windows authentication. | 2024.1.1.17 | Fixed |
TGAL-9757 GCSE-1970 | If you encounter this error "Could not determine key pair for the session. Please try reauthenticating." when saving a workflow to Server UI in previous Designer session, it's because their original session of Designer has expired. The new error message in 24.1 has been changed to the following: "The current session with Server has expired. Please close and re-open Designer to re-authenticate.” | 2024.1.1.17 | Fixed |
TGAL-9760 GCSE-1830 | Controller token and MongoDB password is intermittently becoming corrupt causing service issues as a result. | 2024.1.1.17 | Fixed |
TGAL-10130 | Unable to upload Macro type workflow in Server through UI and public API. | 2024.1.1.17 | Fixed |
TGAL-10137 GCSE-1908 | Recurring Schedule with End date time scheduled in a different Timezone than Server will stop early or run past the End time. | 2024.1.1.17 | Fixed |
TGAL-10138 GCSE-1966 | Schedule Workflow does not use correct Timezone in Monthly schedules when Server and User Timezone are different. | 2024.1.1.17 | Fixed |
TGAL-10184 GCSE-2023 | 2022.3 CryptoMigration is not re-encrypting the User Default Credential - Error running workflow: AlteryxService_RetrieveSecureData failed. | 2024.1.1.17 | Fixed |
TGAL-10609 GCSE-2123 | When upgrading to 2024.1, schema migration 41 will fail if Server UI has custom site colors set. | 2024.1.1.17 | Fixed |
TPRI-1683 | Issues with default worker when editing schedules in Server. | 2024.1.1.17 | Fixed |
TPRI-2353 GCSE-1504 | Nested links in Server UI are all at the same level of indentation. | 2024.1.1.17 | Fixed |
TPRI-3334 | Editing a Scheduled workflow to back date is allowed in Server. | 2024.1.1.17 | Fixed |
TPRI-3344 | Recurring schedule: Weekly scheduling a workflow is failing in Server. | 2024.1.1.17 | Fixed |
TPRI-3661 GCSE-1757 | In the Date Tool, you can only select the year when you drill down and not the month. For the month, you must navigate right and left until the required month is selected. | 2024.1.1.17 | Fixed |
TPRI-3662 GCSE-1758 | In the File Browse Tool, when you are mapping fields to an app, it is not as visually distinct as in previous Server versions. | 2024.1.1.17 | Fixed |
TPRI-3820 TGAL-8887 | Users are unable to update tags after assigning max number of (5) tags. | 2024.1.1.17 | Fixed |
TPRI-3821 TGAL-8904 | Permission state is not getting reset despite closing. | 2024.1.1.17 | Fixed |
TPRI-3839 GCSE-1743 | After selecting a date in the Date Tool on Alteryx Server, the format of the display date changes from DD/MM/YYYY in previous versions (for example, 2021.3) to MM/DD/YYYY. | 2024.1.1.17 | Fixed |
TPRI-3904 TGAL-8892 | Filter is not working for Tags in Server UI. | 2024.1.1.17 | Fixed |
TPRI-3922 TGAL-8886 | User is not able to Set Default value for "Forecast Refresh Interval". | 2024.1.1.17 | Fixed |
TPRI-4024 GCSE-1590 | Starting 2023.1, owners of Public workflows can’t see the workflows under My Files, just in the Public tab of My Workspace. In 2022.1, Public workflows are visible in both My Files and Public tabs. | 2024.1.1.17 | Fixed |
TPRI-4027 GCSE-1537 | Server schedules are showing a different ending time based on the users Timezone from what was originally scheduled when editing the schedule. | 2024.1.1.17 | Fixed |
TPRI-4100 GCSE-1822 | Chain applications require manual run for each analytics app even if the analytics app does not have any user input required. | 2024.1.1.17 | Fixed |
TPRI-4300 | Searching a user name under migration drop down its not giving any search results after entering username. | 2024.1.1.17 | Fixed |
TPRI-4396 GCSE-1950 | In Server Admin interface, Collections > Collection > Workflows > Added to Collection sort is sorting alphabetically instead of by date. | 2024.1.1.17 | Fixed |
TPRI-4580 TGAL-8884 | Schedule Name is appearing while editing the schedule. | 2024.1.1.17 | Fixed |
TPRI-5079 | The radio button analytical app's default value functionality is broken, producing incorrect output. | 2024.1.1.17 | Fixed |
TPRI-5094 GCSE-2073 | File Browse Tool does not show complete text in Server UI. | 2024.1.1.17 | Fixed |
TPRI-5145 GCSE-2082 | Chained apps on Server are run despite errors. | 2024.1.1.17 | Fixed |
TPRI-5308 | When a user changes the start time or enables the end time of a scheduled workflow, the checkbox gets deselected. Each time a schedule modification is performed, the user must enable the checkbox. | 2024.1.1.17 | Fixed |
Fixed Minor Release Version 2024.1.1.49 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-1043 GCSE-1974 | Users with Chinese characters in their Alteryx Server UI logon name are not able to publish workflows to their Server. | 2024.1.1.49 | Fixed |
TGAL-10571 | Error message when transferring asset to member that doesn't have the correct role needs to be updated. | 2024.1.1.49 | Fixed |
TGAL-10727 | Individual select box is getting blank/unchecked after transferring multiple workflows/schedules together. | 2024.1.1.49 | Fixed |
TGAL-10747 | Clearing "Run As" credentials allows the workflow to run as default user even when the setting has been set to Require Credentials. | 2024.1.1.49 | Fixed |
TGAL-10748 | Incorrect permission error is displayed to the new owner after transferring workflow or schedule, even if they have the permission to access the workflow or schedule. | 2024.1.1.49 | Fixed |
TGAL-10749 | When transferring ownership of a workflow but no schedules to another user, the resulting snackbar on the bottom left side of the page says “Transferred workflow and schedules,” when it should say “Transferred workflow.” | 2024.1.1.49 | Fixed |
TGAL-10754 | Unable to reset the Theme settings back to default in Server. | 2024.1.1.49 | Fixed |
TGAL-10792 GBETA-452 | When transferring schedule ownership to another user, an incorrect error message is displayed and remains on the screen even though it should no longer be visible. | 2024.1.1.49 | Fixed |
TGAL-10793 GBETA-453 | When a user installs the Server API tool in Designer and creates a workflow calling GET /v3/workflows, they see the following error in their UI: Alteryx.Server.Models.Engine.AppValidation+AppValidationMessage. | 2024.1.1.49 | Fixed |
TGAL-10805 | When a user installs the Server API tool in Designer and creates a workflow calling GET /v3/workflows, no further validation message is displayed within the window. | 2024.1.1.49 | Fixed |
TGAL-10822 | When bulk transferring ownership of workflows or schedules, the resulting snackbar should accurately reflect what was actually transferred regardless of the radio button that was selected. | 2024.1.1.49 | Fixed |
TGAL-10846 | The POST API request to the /admin/v1/workflows endpoint in order to upload workflow returns an error message in the FIPS version of Server. | 2024.1.1.49 | Fixed |
TGAL-11089 GCSE-2250 | AlteryxService fails to start up when configuring Alteryx Designer for Designer and Scheduler Only on 2024.1. | 2024.1.1.49 | Fixed |
TGAL-11090 | When using a shared Run As credential, clearing the Run As checkbox and adding new credentials results in using the old credentials instead of the supplied ones. | 2024.1.1.49 | Fixed |
TPRI-5380 GCSE-2151 | Analytic app > Interface Designer > On Success > No Output Files Message doesn't appear when run on Server. | 2024.1.1.49 | Fixed |
TPRI-5432 TGAL-10764 | Newly added collections are not visible in Server UI without manual refresh of the webpage. | 2024.1.1.49 | Fixed |
Fixed Minor Release Version 2024.1.1.71 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TPRI-5661 GCSE-2007 | The third chained app does not load the output file generated by the first app when running on Server. | 2024.1.1.71 | Fixed |
Fixed Minor Release Version 2024.1.1.93 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
GDCM-4147 | DCM concurrent sharing is not working when Key file is used. The workflow fails with error "Failed to complete write to Google BigQuery: Function not implemented." when run on Server. | 2024.1.1.93 | Fixed |
TCPE-1033 GCSE-2035 | Email events, created with each workflow, intermittently send blank emails with the correct email as soon as the expected event email is sent. | 2024.1.1.93 | Fixed |
TCPE-1111 GCSE-2229 | After upgrading Server from 2021.4.2.47802 to 2022.1.1.42691, and then to 2023.2.1.133, the following error appears "Error running Event #1: Func 'curl_easy_perform' failed, ret = 8, desc = Weird server reply" on workflows with email event. | 2024.1.1.93 | Fixed |
TGAL-11407 | When you run the seeded SqlServer DB and navigate to Credentials, an exception is thrown. The Credentials table is shown with a single row that says “ERR”. | 2024.1.1.93 | Fixed |
Fixed Minor Release Version 2024.1.1.136 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TDYN-761 GCSE-2376 | Server UI: There is a 30-character limitation in DCM Connections for Snowflake DSN-less that prevents connections to databases whose name contains more than 30 characters with the error "Validation failed. The input exceeds maximum allowed length." | 2024.1.1.136 | Fixed |
TGAL-11249 GCSE-2339 | The reindex command line does not generate logging in 2024.1. | 2024.1.1.136 | Fixed |
TGAL-11268 GCSE-2338 | The CryptoMigration log (AlteryxServiceMigrator_#.log) incorrectly categorizes the new error as state ;4; instead of ;3;. | 2024.1.1.136 | Fixed |
TGAL-11272 TPRI-1122 | New Server UI: In both user and admin Schedules, the schedule status filter does not work. When users select or clear any of the checkbox options in the filter for the Status column, an empty page with the "No Schedules." message is displayed. | 2024.1.1.136 | Fixed |
TGAL-11282 GCSE-2344 | Crypto Migration Summary counts for PackageDefinitions and AppChunks do not match as expected. | 2024.1.1.136 | Fixed |
TGAL-11440 GCSE-2431 | SQL Server DB schedules do not run the published version of the workflow, but the version from when the schedule was created. | 2024.1.1.136 | Fixed |
TGAL-11458 GCSE-2430 | Schema Migration 49 is failing on upgrades to 2024.1 if various Messages, DatasetMessages, or TagIds arrays in appInfos records are missing or contain null values. | 2024.1.1.136 | Fixed |
TGAL-11459 GCSE-2442 | When upgrading from 2021.4 to 2024.1, Gallery schema migration will fail and prevent Server from loading post upgrade. | 2024.1.1.136 | Fixed |
TGAL-11460 GCSE-2437 | When migrating to 2024.1, Server will fail to migrate with the Migration 49 error when the Filename field in the PrimaryApplication object within a revision is invalid or contains an empty name. | 2024.1.1.136 | Fixed |
TPRI-5954 GCSE-2346 | Tree tool in a chained app does not work when running on Server 2023.1 Patch 7. | 2024.1.1.136 | Fixed |
TPRI-6408 GCSE-2526 | Schedule does not work for Analytic Apps. | 2024.1.1.136 | Fixed |
Fixed Minor Release Version 2024.1.1.168 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-1033 GCSE-2035 | Email events, created with each workflow, intermittently send blank emails with the correct email as soon as the expected event email is sent. | 2024.1.1.168 | Fixed |
TCPE-1265 GCSE-2579 | The SharePoint tool (version 2.1.0) running on Server 2.1.0 generates numerous field conversion errors, exceeding the MongoDB document size limit of 16GB. As a result, no document is created in the AS_Results collection, but an error appears in the AS_Queue collection. | 2024.1.1.168 | Fixed |
TGAL-8401 GCSE-1474 | Updating the Input Data Tool with the action type "Update Input Data Tool (Default)" fails in the Server UI when using the POST /users/v2/Workflows/{appid}/jobs endpoint. | 2024.1.1.168 | Fixed |
TGAL-11891 GCSE-2648 | When upgrading from Alteryx Server 2022.1 to 2024.1, Alteryx Gallery migration fails on 40.01, with error deserializing the CustomCss property. | 2024.1.1.168 | Fixed |
TGAL-11965 | When using the GET /admin/v1/subscriptions endpoint, a 500 Internal Server Error appears. | 2024.1.1.168 | Fixed |
TGAL-11968 | When syncing Azure AD Groups by SCIM, a 500 Internal Server Error occurred. | 2024.1.1.168 | Fixed |
TGAL-11983 | When using the GET /admin/v1/users endpoint, a 500 Internal Server Error appears. | 2024.1.1.168 | Fixed |
TPRI-5918 GCSE-1508 | Theme colors apply to curators only. | 2024.1.1.168 | Fixed |
TPRI-6498 GCSE-2584 | The Job Results page becomes unresponsive and fails to load log messages when the log size is excessively large. This can eventually result in either a RESULT_CODE_HUNG or an "Out of Memory" error. | 2024.1.1.168 | Fixed |
Known Issues
Known Major Release Version 2024.1.1.17 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-812 GCSE-1619 | When using the “£” character in Server credentials, the workflow using the same credentials have failed to execute with the error "The username or Password is Incorrect". | 2024.1.1.17 | Known |
TCPE-820 GCSE-1629 | SAML login is sending the incorrect timestamp for the "IssueInstant" attribute when login is initiated from the Server to the IDP. | 2024.1.1.17 | Known |
TCPE-869 GCSE-1742 | When deleting a workflow in Server UI, an error "Failed to delete Workflow XXX" occurs. | 2024.1.1.17 | Known |
TCPE-897 GCSE-1859 | When uploading a workflow to Server either via API or through Designer for previous version, the "versionNumber" field returns 0. | 2024.1.1.17 | Known |
TCPE-912 GCSE-1851 | When a workflow is renamed in Server UI and then opened in Designer, then the new workflow name in Metainfor is not being retrieved in Designer. | 2024.1.1.17 | Known |
TCPE-931 GCSE-1896 | After upgrade to 2023.1+, users can’t see their workflows in their Workspace. They can see workflows shared with them and newly published workflows only. | 2024.1.1.17 | Known |
TCPE-936 GCSE-1582 | While migrating Designer Schedules to Server, it's not possible to find some existing users who are not among the first 25 users. | 2024.1.1.17 | Known |
TCPE-951 GCSE-1523 | Run As is not running the workflow with the correct credentials on Server. | 2024.1.1.17 | Known |
TCPE-960 GCSE-1938 | When submitting a workflow version via API as a user other than the workflow owner (for example, using the API credentials of a service account), the subscription of the workflow is changed to the API owner's. | 2024.1.1.17 | Known |
TCPE-976 GCSE-1959 | Schedules > Filter by Owner only finds first 15 users. Typing a name to search will only search within these 15 user names. | 2024.1.1.17 | Known |
TCPE-977 GCSE-1958 | Schedules > Filter by Owner doesn't load for Artisans. | 2024.1.1.17 | Known |
TCPE-980 GCSE-1961 | Server UI is not able to display a preview for PCXML file if a URL or hyperlink is output to a Render tool. The following error occurs: "Error: Unable to Load Preview". | 2024.1.1.17 | Known |
TCPE-1033 GCSE-2035 | Email events, created with each workflow, intermittently send blank emails with the correct email as soon as the expected event email is sent. | 2024.1.1.17 | Known |
TCPE-1057 GCSE-2080 | DCM page load issues due to missing trailing slashes in requests. | 2024.1.1.17 | Known |
TCPE-1065 GCSE-2089 | Administrator fails to update user profile in Japanese UI. | 2024.1.1.17 | Known |
TCPE-1072 GCSE-2084 | Curator has access to workflows uploaded by other users via URL and workflow ID. | 2024.1.1.17 | Known |
TCPE-1073 GCSE-2093 | The GET v3/collections endpoint is showing the USER ID as null for a collection API. | 2024.1.1.17 | Known |
TCPE-1080 GCSE-2138 | When switching to different subscriptions and returning to the original one, existing schedules encounter an error stating: "You do not have access to this workflow. To request access, please contact the author or your administrator." | 2024.1.1.17 | Known |
TCPE-1086 GCSE-2139 | When calling the /v3/workflows/{workflowId}/package endpoint, the temporary file stored on Server following pattern "_axc_****.yxzp" is not deleted. | 2024.1.1.17 | Known |
TCPE-1090 GCSE-2147 | A workflow from a newer, non-compatible version of Designer can be published to an older version of Server and scheduled to run successfully. Manually running the workflow will give an "The application could not be found" error. | 2024.1.1.17 | Known |
TCPE-1092 GCSE-2152 | User can proceed to the Run page of the workflow with incorrect credentials set as default on Server. | 2024.1.1.17 | Known |
TCPE-1223 GCSE-2457 | Receiving the “Page not Found“ error after IDP-initiated login with certain IDPs as well as normal login with others. Exception thrown when asserting SAML response from IDP. | 2024.1.1.17 | Known |
TCPE-1247 GCSE-2553 | Desktop Automation Schedule times change after upgrade to 2024.1 by the number of hours difference the machine’s timezone is from UTC. | 2024.1.1.17 | Known |
TCPE-1294 GCSE-2691 | Unable to connect 2024.1 Designer to a 2024.1 Server on a lower patch version. | 2024.1.1.17 | Known |
TGAL-8263 GCSE-1184 | API V3: Schedule PUT API allows the priority to be changed when the user profile does not have access. | 2024.1.1.17 | Known |
TGAL-8314 GCSE-1374 | A workflow manually run from Server UI that requires user credentials is running as the local user, rather than the user credentials that were entered when 'Make these my default credentials.' is selected. | 2024.1.1.17 | Known |
TGAL-8534 GCSE-1534 | Last App in series of at least 3 chained Apps fails to read the output file from the first App. | 2024.1.1.17 | Known |
TGAL-8692 GCSE-1674 | Workflow status shows as corrupted that runs via Scheduler on the Controller node. | 2024.1.1.17 | Known |
TGAL-8841 GCSE-1622 | Excel file output appears to be corrupt when retrieved from Server API call GET /v1/jobs/{id}/output/{outputId}. | 2024.1.1.17 | Known |
TGAL-9626 GCSE-1931 | Unable to upload workflow using V3 API when CredentialID contains Custom Groups. | 2024.1.1.17 | Known |
TGAL-10286 GCSE-2039 | Workflows and analytics apps which includes macro gets converted into macro while publishing them using the following Server API endpoints: POST /admin/v1/workflows and POST /v3/workflows. | 2024.1.1.17 | Known |
TGAL-10628 GCSE-1993 | Base Map Tiles are not rendering in Server UI as expected in Server UI and Sandbox environment. | 2024.1.1.17 | Known |
TGAL-10737 GCSE-1703 | In the Admin > Jobs page under the Status tab, when you sort by State column, it's sorting based on the Schedule Time/createDate. | 2024.1.1.17 | Known |
TGAL-10747 | Clearing "Run As" credentials allows the workflow to run as default user even when the setting has been set to Require Credentials. | 2024.1.1.17 | Known |
TGAL-10748 | Incorrect permission error is displayed to the new owner after transferring workflow or schedule, even if they have the permission to access the workflow or schedule. | 2024.1.1.17 | Known |
TGAL-10755 GCSE-2178 | Workflow icon uploaded by workflow owner in Home page is removed after downloading and reuploading via API. | 2024.1.1.17 | Known |
TGAL-10792 GBETA-452 | When transferring schedule ownership to another user, an incorrect error message is displayed and remains on the screen even though it should no longer be visible. | 2024.1.1.17 | Known |
TGAL-10793 GBETA-453 | When a user installs the Server API tool in Designer and creates a workflow calling GET /v3/workflows, they see the following error in their UI: Alteryx.Server.Models.Engine.AppValidation+AppValidationMessage. | 2024.1.1.17 | Known |
TGAL-10805 | When a user installs the Server API tool in Designer and creates a workflow calling GET /v3/workflows, no further validation message is displayed within the window. | 2024.1.1.17 | Known |
TGAL-10846 | The POST API request to the /admin/v1/workflows endpoint in order to upload workflow returns an error message in the FIPS version of Server. | 2024.1.1.17 | Known |
TGAL-11185 GCSE-2288 | When creating a new MongoDB in 2022.3 - 2023.2, the AS_Versions collection is not created if RuntimeSettings.xml containing <MigrationVersionNumber>1</MigrationVersionNumber> exists at the time of the MongoDB creation. If AS_Versions doesn’t exist at the time of an upgrade, the crypto migration process is initiated and fails. This then prevents the AlteryxService from starting post upgrade. This issue does NOT occur if you are on the newest patches, specifically 2023.1.392+, 2023.2.173+, and 2024.1.1.17+. | 2024.1.1.17 | Known |
TGAL-11767 GCSE-2569 | When upgrading from a Server version starting with the major version of 2021.4 up to (and including) 2021.4.2.40860 Patch 4 directly to 2024.1, the schema migration fails, leading to a 404 error in Server. To avoid this defect, we recommend an intermediary upgrade to a version between (2022.3 - 2023.2) before upgrading to 2024.1. | 2024.1.1.17 | Known |
TGAL-11869 GCSE-2533 | Schedule times off by # of hours user is off from UTC after upgrade to 2024.1. | 2024.1.1.17 | Known |
TGAL-11891 GCSE-2648 | When upgrading from Alteryx Server 2022.1 to 2024.1, Alteryx Gallery migration fails on 40.01, with error deserializing the CustomCss property. | 2024.1.1.17 | Known |
TGAL-11949 | Unable to delete credentials after adding or removing users from Subscriptions, and incorrect message displayed stating that the credentials have been deleted. | 2024.1.1.17 | Known |
TGAL-11965 | When using the GET /admin/v1/subscriptions endpoint, a 500 Internal Server Error appears. | 2024.1.1.17 | Known |
TGAL-11968 | When syncing Azure AD Groups by SCIM, a 500 Internal Server Error occurred. | 2024.1.1.17 | Known |
TGAL-11983 | When using the GET /admin/v1/users endpoint, a 500 Internal Server Error appears. | 2024.1.1.17 | Known |
TPRI-4025 GCSE-1589 | Issues with collection workflow search interaction: When typing a workflow name into search that is not a workflow in Server UI, it immediately displays "No workflows to add.", which makes it seem like there are no workflows. | 2024.1.1.17 | Known |
TPRI-4053 GCSE-1057 | Server Usage Report shows ExecutionTime of job as 0. | 2024.1.1.17 | Known |
TPRI-4712 GCSE-1787 | When Analytic App runs in Server UI, File Browse tool does not use the correct file path when an input file is selected. | 2024.1.1.17 | Known |
TPRI-5409 GCSE-2154 | Radio buttons and Labels are out of order in Server UI. | 2024.1.1.17 | Known |
TPRI-5461 GCSE-1704 | Windows Auth: Email column field displays Windows Identity Name and not the Email address. The column field header should be Windows Identity. | 2024.1.1.17 | Known |
Security Updates
Fixed Major Release Version 2024.1.1.17 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TDS-765 | We have updated the embedded OpenSSL library to version 3.0.12. This patch-level release does not change API/ABI functionality or interoperability. It addresses the presence of several reported potential vulnerabilities within the OpenSSL codebase, including:
See https://www.openssl.org/news/openssl-3.0-notes.html for more information. | 2024.1.1.17 | Fixed |
TGAL-7140 | To be disclosed.* | 2024.1.1.17 | Fixed |
Minor Release Version 2024.1.1.168 | |||
TGAL-11764 GVM-1325 | To be disclosed.* | 2024.1.1.168 | 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.