Release Note Product Versions | |||
|---|---|---|---|
Version | Release Date | Release | End of Support |
2025.1.1.27 | May 13, 2025 | Major | May 13, 2027 |
2025.1.1.31 2025.1.1.1.31 (Patch 1) | June 16, 2025 | Minor/Patch | May 13, 2027 |
Warning
This section contains important updates regarding the 2025.1 release. Please review these items before you upgrade.
With the end of support for version 2022.3 on November 29, 2024, Crypto Migrator and its related code have been removed in version 2025.1.
To migrate from Server 2022.1 or earlier, you must first upgrade to Server 2023.2 or 2024.1 in order to upgrade MongoDB to version 7. For detailed migration steps, see the Server 2024.2 Release Notes.
The Alteryx Server version 2025.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 2025.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.
To enhance visibility and ensure proper governance of the Server software, we now log configuration changes made by admins with access to the Alteryx Server's host machines. When an admin updates System Settings and confirms the changes by selecting the final Confirm button, the details are recorded in a flat log file. This log is stored on the same machine as the Runtime Settings file at C:\ProgramData\Alteryx. Access to this log file is restricted to Windows accounts with administrative permissions.
We've added a new Admin Workflow Results and Job messages view. This enables Admins to see a list of workflow results and expand individual job records. You can see detailed job messages for workflows with statuses such as Running, Queued, Completed, Failed, Errored, Cancelled, or Warning. For more information, go to Workflow Results: Admin Interface.
Non-admin users now have access to a Credentials page in the Server UI. This page allows you to view, create, edit, and delete custom credentials. You can also set credentials for running and scheduling workflows in Workflows.
The Credentials page includes 3 tabs:
All – Displays all credentials available to you.
My Credentials – Shows credentials you have created via My Profile or Credentials, as well as those created through the Workflows or Schedules page.
If custom credentials used in My Profile are already saved by an admin or another non-admin user, they won’t appear on your My Credentials page, but you will still be able to use them. These credentials are visible under the Default Credentials section.
Shared With Me – Lists credentials shared with you by Server admins.
You can sort and filter credentials for easier management.
In Workflows, you can select credentials to Run and Schedule a workflow. You can enter new credentials, use previously entered ones, or select credentials shared with you.
When associating credentials with a workflow from Designer, you can manage those credentials from the newly introduced Credentials tab in Server. These credentials will also be available in the dropdown for future use—both in Designer and in Server.
For shared credentials or service accounts, the correct approach is to manage them through the Admin Credentials page. An admin should either create the credentials or invite a user to create them, and then share them with others via the Admin Credentials page. If shared credentials are used directly by multiple users without being shared by an admin, the credentials will be associated with the first user. All other users will not see these credentials in their My Credentials tab.
For more details, refer to Credentials: Server User Interface.
With the new Credentials page available to non-admin users, admins can now invite users to create or edit credentials when a password update is required. Users receive notifications for admin invitations, shared credentials, and invalid credentials. This enhancement helps reduce security risks. For more details, see Invite to Create or Edit a Credential.
We've added the DELETE /v3/jobs/{jobId} endpoint, allowing users to cancel any running or queued job—whether manual or scheduled—on Alteryx Server.
Curators can cancel any job.
Other roles can cancel jobs they have created, triggered, or scheduled. It includes jobs shared with them through Collections, even if they are not the job owner.
For more details, go to Job Endpoints.
We've added two API credential endpoints for Server credentials (non-DCM):
Create Server credentials:
POST /v3/credentialsUpdate password for existing Server credentials:
PUT /v3/credentials/{credentialId}
These endpoints are available only to Curators and require TLS to be enabled. For more information, refer to the Credential Endpoints help page.
We've added a dynamic scheduling flexibility by using Cron entries to align with the experience provided to cloud users and for a consistent experience across the various products in our platform.
You can now use Cron expressions in the following API endpoints:
POST /v3/schedulesPUT /v3/schedules/{scheduleId}PATCH /v3/schedules/{scheduleId}GET /v3/schedules/{scheduleId}
Limitations of Cron Expression Support
While this release introduces enhanced scheduling flexibility using Cron expressions, there are some current limitations to be aware of:
No support for combining range (-) and step (/) characters within the same expression.
Invalid expression:
0 23 * 1-11/2 * *Valid expression :
0 23 * 2,4,6,8,10 * *Five-Field Cron format only.
This implementation supports only the five-field Cron format:
minute hour day-of-month month day-of-weekStep values are not supported in the day-of-week (last) field.
Invalid expression:
0 * * * */tueValid expression:
0 * * * TUE
For more details, visit the Schedule Endpoints help page.
Important
These new endpoints apply only to customers on the new Edition based pricing, launched in May 2025 for eligible customers.
Online customers: Usage data is automatically collected and sent to Alteryx Analytics Cloud at regular intervals. Admins can review this data directly in Alteryx Analytics Cloud.
Offline customers: Offline customers must use Alteryx Analytics Cloud for licensing and billing. The usage data report will not be automatically sent to Alteryx Analytics Cloud. However, you can manually extract and upload the report via the API endpoints available on Server and Alteryx Analytics Cloud.
For detailed steps on extracting and loading usage data to Server, please refer to Server Usage Endpoints.
To enhance security, we now support SAML assertion encryption, allowing you to both encrypt and sign assertions. This feature is available in both FIPS and non-FIPS environments.
For configuration details, see the Configure Alteryx Server Authentication help page.
Fixed Major Release Version 2025.1.1.27 | |||
|---|---|---|---|
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. | 2025.1.1.27 | Fixed |
TCPE-1201 GCSE-2416 | Workflows uploaded via API do not execute when the user has default credentials set in My Profile. | 2025.1.1.27 | Fixed |
TCPE-1218 GCSE-2443 | When the Email Tool attachment size limit is exceeded, messages are intermittently sent blank or garbled. | 2025.1.1.27 | Fixed |
TCPE-1231 GCSE-2488 | Editing scheduled workflows created one day prior to the current date results in an error for users. | 2025.1.1.27 | Fixed |
TCPE-1263 GCSE-2602 | Redirection from #!app to #!/app does not occur on first-time access to a direct workflow URL. | 2025.1.1.27 | Fixed |
TCPE-1264 GCSE-2601 | The Edit button is missing for schedule owners who do not own the associated workflow in 2024.1. | 2025.1.1.27 | Fixed |
TCPE-1265 GCSE-2579 | The SharePoint tool (version 2.1.0) running on Server version 2023.2.1 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. | 2025.1.1.27 | Fixed |
TCPE-1294 GCSE-2691 | Unable to connect 2024.1 Designer to a 2024.1 Server on a lower patch version. | 2025.1.1.27 | Fixed |
TCPE-1318 GCSE-2739 | The app interface fails to load in the Server UI when a List Box attempts to load values from an external YXDB file. | 2025.1.1.27 | Fixed |
TCPE-1324 GCSE-2747 | When running a chained app with 5 or more apps in the Server UI, interface questions stop appearing starting from the fifth app and onward. | 2025.1.1.27 | Fixed |
TCPE-1327 GCSE-2758 | When opening and running an Analytic App via File Explorer or Command Prompt, the date format displays as mm/dd/yyyy instead of the selected yyyy-mm-dd, despite the correct format being set in user settings. | 2025.1.1.27 | Fixed |
TCPE-1357 GCSE-2877 | The Help and Info section for DCM - SDK (Gallery) Tools Support in Alteryx System Settings is incorrect. | 2025.1.1.27 | Fixed |
TCPE-1379 GCSE-2855 | Upgrade to Mongo 6.0 will not restore ASMongoDBVersion.bin to the new Mongo6.0 persistence folder, leading to a "Could not finalize MongoDB restore. The MongoDB database failed to start with exit code: 100." error. | 2025.1.1.27 | Fixed |
TCPE-1393 GCSE-2883 | Owner of the workflow is unable to open the workflow when download is disabled for other users. | 2025.1.1.27 | Fixed |
TCPE-1400 GCSE-2902 | Gallery Schema Migration 40.03 fails with error: "Unable to cast object of type 'MongoDB.Bson.BsonNull' to type 'MongoDB.Bson.BsonString'" or "Migration to version 40.03 failed: Renaming collection from 'dataConnections' to 'dataConnectionsMigrationInProcess_40.03'". | 2025.1.1.27 | Fixed |
TCPE-1423 GCSE-2934 | When using SCIM, the role defaults to Viewer instead of Default when SCIM sync runs. | 2025.1.1.27 | Fixed |
TCPE-1429 GCSE-2947 | Unable to retrieve the MongoDB password via Command Prompt when Designer is set to a non-English language. | 2025.1.1.27 | Fixed |
TCPE-1453 GCSE-2990 | When using the | 2025.1.1.27 | Fixed |
TCPE-1468 GCSE-3023 | Numeric Up Down is not showing the decimal in the Server UI. | 2025.1.1.27 | Fixed |
TCPE-1486 GCSE-3039 | After the upgrade, incorrect Designer version is displayed in Version History when uploading new versions of a workflow. | 2025.1.1.27 | Fixed |
TCPE-1496 GCSE-3074 | The othersCanViewHistory value is not changing via | 2025.1.1.27 | Fixed |
TCPE-1504 | The existence of | 2025.1.1.27 | Fixed |
TGAL-8263 GCSE-1184 | API V3: Schedule PUT API allows the priority to be changed when the user profile does not have access. | 2025.1.1.27 | Fixed |
TGAL-11869 GCSE-2533 | Schedule times off by # of hours user is off from UTC after upgrade to 2024.1. | 2025.1.1.27 | 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. | 2025.1.1.27 | Fixed |
TGAL-11896 TDES-7222 | Workflows fail to display output in Server when the output file name exceeds 128 characters. | 2025.1.1.27 | Fixed |
TGAL-11942 | A subscription user is unable to view the analytic app wizard values of the subscription owners schedule on the | 2025.1.1.27 | Fixed |
TGAL-11943 | A subscription user is unable to update analytic app wizard values on the following schedule endpoints: | 2025.1.1.27 | Fixed |
TGAL-11961 | When using the | 2025.1.1.27 | Fixed |
TGAL-11965 | When using the | 2025.1.1.27 | Fixed |
TGAL-11968 | When syncing Azure AD Groups by SCIM, a 500 Internal Server Error occurs. | 2025.1.1.27 | Fixed |
TGAL-11983 | When using the | 2025.1.1.27 | Fixed |
TGAL-11985 | Users with access to a schedule through a collection should not have the ability to delete the schedule. | 2025.1.1.27 | Fixed |
TGAL-11993 | The | 2025.1.1.27 | Fixed |
TGAL-12005 | Making a POST schedule call with Analytic App wizard values results in a 500 error "AES256 payload decryption failed". | 2025.1.1.27 | Fixed |
TGAL-12016 GCSE-2732 | Null values in user records cause indexing and login issues after upgrading to version 2024.1. | 2025.1.1.27 | Fixed |
TGAL-12025 | Duplicate Group Name entries are created when Alteryx Server is configured with a user-managed SQL database. | 2025.1.1.27 | Fixed |
TGAL-12026 | After migrating the schedule from Designer to the Server UI, the job name is not visible in the Schedule section, and the page becomes unresponsive when attempting to expand. | 2025.1.1.27 | Fixed |
TGAL-12062 | Deleting the analytic app used to create a schedule results in error when loading the Schedule UI. | 2025.1.1.27 | Fixed |
TGAL-12128 | When upgrading from Alteryx Server 2022.1 to 2024.1, the Alteryx Gallery migration fails on 40.02 with an error deserializing the CustomCss property. | 2025.1.1.27 | Fixed |
TGAL-12138 GCSE-2794 | The ScheduleOperations job creates excessive CPU and network load (as well as excessive checks) over time and causes Server to stop serving requests. | 2025.1.1.27 | Fixed |
TGAL-12176 GCSE-2812 | Problems occur when using the Make these my default credentials option while running workflows. | 2025.1.1.27 | Fixed |
TGAL-12487 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. | 2025.1.1.27 | Fixed |
TPRI-4358 GCSE-1944 | The | 2025.1.1.27 | Fixed |
TPRI-6363 GCSE-2456 | Chained Analytic App fails to display the second app’s interface and returns a "404 – The application could not be found" error. This occurs when the filename contains a "+" character. | 2025.1.1.27 | Fixed |
TPRI-6626 GCSE-2627 | UI Issue: The Allowed Hosts field does not retain values in the UI after a page refresh. Although the values are saved to the database, they are not displayed in the UI. | 2025.1.1.27 | Fixed |
TPRI-6868 TGAL-11990 | Sorting schedules by workflow name does not work as expected. Instead, it sorts schedules by creation time. | 2025.1.1.27 | Fixed |
TPRI-7113 GCSE-2801 | Chained App Tree Tool does not load data written by a previous app in the chain. | 2025.1.1.27 | Fixed |
TPRI-7318 GCSE-2884 | UI Search: Unable to search for users added in Data Connections. | 2025.1.1.27 | Fixed |
Known Major Release Version 2025.1.1.27 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-1385 GCSE-2874 | Server UI issues after 2024.1 upgrade: Workflows do not appear under My Workspace when searched using the global search. In some cases, the workflow is missing; in others, it displays as undefined. This typically occurs after ownership of the workflow has been transferred. | 2025.1.1.27 | Known |
TCPE-1418 GCSE-2924 | Theme settings for the Side Navigation set by a Curator are not retained after saving and refreshing the page. | 2025.1.1.27 | Known |
TCPE-1432 GCSE-2949 | lnterface tool list values aren't displaying in Server UI when loaded from shared Server UI Data Connection. | 2025.1.1.27 | Known |
TCPE-1466 GCSE-3019 | The Schedule Forecast in Alteryx Server does not display Saturday schedules when the Server UI user’s time zone is set significantly west of UTC, and does not display Sunday schedules when the time zone is set significantly east of UTC. | 2025.1.1.27 | Known |
TCPE-1500 GCSE-3084 | 24.2 Alteryx System Settings does not allow setting Worker >Workflows allowed to run simultaneously to 1. The setting is not saved and reverts to an automated value of 2+ (depending on the number of cores) the next time Alteryx System Settings is opened. | 2025.1.1.27 | Known |
TCPE-1506 GCSE-3097 | Unable to reset passwords for manually created accounts when using Built-In Authentication. | 2025.1.1.27 | Known |
TCPE-1519 GCSE-3122 | Users are unable to schedule a recurring workflow to run on the first Monday of the month when the Server UI language is set to French. Workaround: Change the Server UI language to English, then reschedule the workflow as usual. | 2025.1.1.27 | Known |
TCPE-1525 GCSE-3135 | SAML authorization success message appears garbled on a Japanese operating system. | 2025.1.1.27 | Known |
TCPE-1527 GCSE-3139 | Users are unable to disable Notifications when Alteryx Server is installed on a Windows operating system with the Japanese locale. Workaround: Install Alteryx Server on a Windows system with the English locale. | 2025.1.1.27 | Known |
TCPE-1528 GCSE-3137 | When custom theme colors are applied to the Alteryx Server UI, the Sign In button retains its default color, resulting in a mismatch with the custom header styling. | 2025.1.1.27 | Known |
TCPE-1529 GCSE-3138 | When an admin user changes the Server UI language from English to Japanese, the Email Notifications Actions List remains untranslated. | 2025.1.1.27 | Known |
TCPE-1531 GCSE-3126 | The File Browse Tool is unable to upload very large files (200MB or larger). | 2025.1.1.27 | Known |
TCPE-1535 | Gallery logs are not capturing the majority of activity. | 2025.1.1.27 | Known |
TCPE-1542 GCSE-3168 | Map rendering via Output Preview remains on "Loading..." for SpatialObj in Gallery when SSL is enabled | 2025.1.1.27 | Known |
TCPE-1546 GCSE-3177 | Alteryx Server, when using SQL Server persistence on a dedicated Server node, can fail to create the database or fail to connect to the database. | 2025.1.1.27 | Known |
TCPE-1549 GCSE-3188 | Error occurs when saving workflows to the Server UI: “There is no valid metadata for outgoing connection 1. Run the workflow to generate valid metadata.” This happens with any workflow that includes a macro containing a Python tool. | 2025.1.1.27 | Known |
TCPE-1553 GCSE-3193 | Alteryx Server UI: Workflow fails to output results when all values are selected in the List Box from the File Browse tool. | 2025.1.1.27 | Known |
TCPE-1554 GCSE-3197 | With Safe Mode set as the default in System Settings, changing a workflow to Unrestricted still does not allow the workflow to run. | 2025.1.1.27 | Known |
TCPE-1556 GCSE-3205 | The | 2025.1.1.27 | Known |
TGAL-6870 GBETA-337 | Server UI: Error messages are not translated into the selected language. | 2025.1.1.27 | Known |
TGAL-8982 GCSE-1713 | When selecting Alteryx Database as Browse Everywhere as the file type, the output is generated as a YXDB file instead of the expected YXBE file. | 2025.1.1.27 | Known |
TGAL-11104 GCSE-1604 | Server UI Workflow Version History incorrectly shows older Designer version after workflow is initially resaved with newer Designer version. | 2025.1.1.27 | Known |
TGAL-12017 | When an admin set in Server System Settings changes their role to a non-Curator role, the UI incorrectly displays a success message. | 2025.1.1.27 | Known |
TGAL-12294 TPRI-7283 | Chained Analytic Apps that use the Tree Tool or Date Tool fail to run on Server. | 2025.1.1.27 | Known |
TGAL-12714 GCSE-3000 | Server allows HTTP communication even when HTTPS/SSL is enabled for the Server UI. | 2025.1.1.27 | Known |
TGAL-13172 | When using the Workaround: Ensure the endTime field is included in the payload. For example: {
"workflowId": "6819f02ab00678a9b39ec43d",
"iteration": {
"startTime": "2025-05-11T17:40:43.476Z",
"endTime": "2026-05-08T17:40:43.476Z",
"IterationType": "Cron",
"cronContract": {
"cronExpression": "0 9-16 * * 1-5"
}
},
"name": "testing cron",
"comment": "",
"priority": "Default",
"workerTag": "",
"credentialId": "",
"timeZone": "Asia/Kolkata"
} | 2025.1.1.27 | Known |
TPRI-4145 | Customer managed telemetry file has mismatched header and body. | 2025.1.1.27 | Known |
TPRI-4182 TCPE-904 | Preview of PCXML file outputs doesn't always work in the Server UI. | 2025.1.1.27 | 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. | 2025.1.1.27 | Known |
TPRI-6919 GCSE-2724 | Unable to cancel jobs in the queue via the Server UI. While Curators can still cancel running workflows, jobs that are queued but not yet running cannot be canceled or deleted. | 2025.1.1.27 | Known |
TPRI-7016 GCSE-2761 | License Created Notification is still available in Server UI. | 2025.1.1.27 | Known |
TPRI-7150 GCSE-1959 | In Schedules, the search dropdown list displays only the first 15 users (who have rights to Schedule a workflow). Typing a name to search will only search within these 15 user names. | 2025.1.1.27 | Known |
TPRI-7731 GCSE-2975 | Unable to delete any data connections that have been shared with a custom user group from Server UI > Admin > Data Connections. | 2025.1.1.27 | Known |
Major Release Version 2025.1 | ||
|---|---|---|
ID | Description | Version |
TGAL-11764 | Fixed an Insecure Direct Object Reference (IDOR) related to MongoDB object IDs to ensure that users only access objects they are authorized to view. | 2025.1 |
TGAL-11771 GENG-4424 | Upgraded foundational C++ libraries including SQLite (to version 3.45.3) and POCO (to version 1.13.3) to enhance system stability. | 2025.1 |
TGAL-12204 | Replaced DotNetZip with a secure compression library, improving how packaged workflows and ZIP files are handled. | 2025.1 |
TGAL-12461 | Upgraded bundled MongoDB components from version 6.0.5 to 6.0.21. This includes stability and security improvements. | 2025.1 |
TGAL-12706 | Removed unused or outdated front-end libraries including Bootstrap 3.4.1 and Lodash 4.16.1 to reduce legacy dependencies. | 2025.1 |
TGAL-12802 TGAL-12829 | Improved how temporary files are created by adopting randomized names and atomic operations. This ensures consistency and reduces the chance of file collisions. | 2025.1 |
TGAL-12803 | Hardened how dynamic regular expressions are processed across components. This improvement helps prevent workflow slowdowns when handling complex patterns. | 2025.1 |
TPRI-7261 | Upgraded Axios from version 0.21.2 to 1.8.1 to support modern API integrations. | 2025.1 |
Patch/Minor Release Version 2025.1.1.1.31 | ||
TGAL-13294 | A critical authentication bypass vulnerability was discovered in the Alteryx Server product. This flaw allows an unauthorized attacker to create an authenticated session without valid credentials, potentially granting them Administrator-level access to the application. The authentication types impacted are limited to Built-In and SAML. Credit: Diyan Apostolov ICT Strypes EOOD | 2025.1.1.1.31 |