Skip to main content

Server 2025.2 Release Notes

Release Note Product Versions

Version

Release Date

Release

End of Support

2025.2.1.24

December 3, 2025

Major

December 3, 2027

Upgrade Considerations

Warning

This section contains important updates regarding the 2025.2 release. Please review these items before you upgrade.

Decoupled Designer and Server Updates

To modernize the update experience and reduce IT overhead, Alteryx has decoupled Designer and Server updates. This change allows you to upgrade Designer independently from Server, so users can immediately access the latest Designer features without waiting for Server approval or environment upgrades. This improvement streamlines adoption, accelerates access to new functionality, and reduces delays—especially for organizations with lengthy Server update cycles.

With this enhancement, assets built in newer versions of Designer are no longer blocked from being published to older Server environments. Instead of a blocking error, users will now see a warning and can choose whether to proceed, empowering teams with more flexibility while reducing workflow disruptions.

For important details (including potential limitations) and ongoing updates, go to Designer Server Version Compatibility.

Workflow Execution

  • In the 2025.2 release, the previous Designer-Server version compatibility limitations still apply to workflow execution. That is, you can’t execute workflows created in a newer version of Designer than Server.

  • The 2026.1 release will be the first release where you can take advantage of the decoupling between Designer and Server. That is, you can upgrade Designer to 26.1 and save and execute 26.1 workflows in Server 25.2 (noting Potential Execution Impacts).

Upgrade Embedded MongoDB to Version 8

As part of the Server 2025.2 installation, the embedded MongoDB will be automatically upgraded to version 8.

Warning

Review the Schema Version Crosswalk to ensure your upgrade path moves to the same version of MongoDB or only one version higher. You cannot upgrade Server directly across more than one MongoDB version at a time.

For example, if you are currently on MongoDB 6.0 (used in Server 2023.2–2024.1), you must first upgrade to MongoDB 7.0 (Server 2024.2–2025.1) before upgrading to MongoDB 8.0 (Server 2025.2).

Localization Support

All supported languages are functional, and translations have been updated. However, you might notice occasional inaccuracies or inconsistencies, especially in new features. Additional improvements are planned for upcoming patches and the next major release.

New Features

Server Connection to Alteryx One

The Controller page now includes a new Connections – Alteryx One feature. This update simplifies how you connect your Alteryx Server environment to the Alteryx One Platform. It introduces a streamlined way to configure data lineage connections and send lineage metadata from Server to an external data catalog—such as Atlan or Collibra—through Alteryx One.

Admins can now use their Alteryx One Workspace account to authenticate and connect Server to Alteryx One. To enable the integration, generate a Server Link Payload from Alteryx One. Then, paste the payload into the Controller configuration page in Alteryx System Settings and test the connection.

Note

The Service Principal used for Server-Alteryx One communication must have the Admin role in Alteryx One. Custom roles with reduced permissions are not currently supported.

For details on generating and using the Server Link Payload, refer to the Data Lineage Connection and Controller documentation. If your organization uses proxies, make sure to whitelist the required Alteryx Platform Services endpoints.

Updated Server Host Recovery Process

We’ve improved the Server host recovery process to reduce complexity and risk during upgrades or infrastructure changes. Previously, host recovery was highly manual and involved over 40 steps, which often led to hesitation and challenges, especially when migrating from end-of-life operating systems or moving to new environments.

Now, you can choose between 2 recovery paths:

  • Manual Path: Complete each step yourself. This path works best for custom environments or where scripting isn’t available.

  • Scripted Path: Use our new recovery script to automate the first 4 sections—preparation, installation, restoring RuntimeSettings and MongoDB—from the Server Host Recovery Guide. Then complete the remaining steps manually. This reduces manual effort and standardizes recovery, especially when using embedded MongoDB. You can download the script from the License Portal.

For more information on the host recovery process, go to Server Host Recovery Guide.

Server API Updates

New API Endpoint for Monitoring Running Jobs

A new endpoint, GET /v3/jobs, is now available for Curators to efficiently monitor all currently queued and running jobs on the Server. This API returns enriched job data in JSON, including Job ID, Status (Queued, Running, Completed, Initializing), Workflow Name and ID, submitting user, start time, queue time, execution duration, and priority (if applicable).

By providing a comprehensive overview in a single call, Curators can quickly assess system health, detect issues, and automate interventions—without querying jobs one by one. This API endpoint reduces support load, enables faster responses to job queue issues, and empowers Curators to take confident, independent actions such as job cancellations.

For more details about this endpoint, go to Job Endpoints.

Expanding DCM API to Support SDK Connectors

The Data Connection Manager (DCM) API has been expanded to fully support SDK-based connectors, enabling end-to-end lifecycle management via API. This enhancement will enable the automated, API-driven creation, updating, deletion, and retrieval of SDK connector-based connections, unlocking broader automation and integration use cases across cloud and desktop workflows.

For more details, go to DCM Endpoints.

Workflow Endpoints Updated with New Parameter

To support decoupled Designer and Server updates, a new parameter—bypassWorkflowVersionCheck—has been added to the following workflow endpoints:

  • POST /v3/workflows

  • POST /v3/workflows/{workflowId}/versions

With this update, you can now use the bypassWorkflowVersionCheck flag when uploading an asset directly to Server via the REST API. This allows you to bypass the guardrail that typically blocks uploads if the Server version is older than the workflow version. For more details on usage, refer to Workflow Endpoints.

Schedule Analytic Apps Directly from the Server UI

You can now schedule Analytic Apps directly from the Server UI. This feature lets you run apps automatically based on customizable day, time, and recurrence settings. It also allows you to maintain a single, centralized workflow or app while giving you the flexibility to specify different input values for each scheduled run.

To schedule an Analytic App, simply select the app in the Server UI, select Schedule, set your preferences, complete any required input fields, and save the schedule. For more information, refer to the Schedule a Workflow help page.

Credentials UI Enhancements

This update delivers a range of UI improvements to the credentials management experience. It addresses usability feedback, resolves visual inconsistencies, and supports edge-case scenarios not included in the 2025.1 release.

You can now use duplicate credentials—even if they aren’t shared through the Alteryx Server platform.

These enhancements align the Credentials interface with platform standards and user expectations.

React 19 Upgrade

Alteryx Server has been upgraded to React 19, taking advantage of the latest features and performance improvements introduced in the React ecosystem. This upgrade reduces bundle size, streamlines the user experience, and ensures compatibility with the latest Onyx UI components. With React 19 now supported by both Server and Onyx, future upgrades will be smoother and more consistent across Alteryx products.

React Router Upgraded to v7 in Server UI

We’ve upgraded react-router in Server UI from version 5.1.2 to 7.8.2, bringing major improvements in performance, bundle size, and routing flexibility. This update enables more efficient data loading, simpler error handling, and lays the foundation for faster navigation and future feature enhancements.

Fixed and Known Issues

Major Release

Version: 2025.2.1.24

Fixed Issues

Fixed

Major Release Version 2025.2.1.24

ID

Description

Version

Issue Status

TCPE-1418

GCSE-2924

Theme settings for the Side Navigation set by a Curator are not retained after saving and refreshing the page.

2025.2.1.24

Fixed

TCPE-1500

GCSE-3084

2024.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.2.1.24

Fixed

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.2.1.24

Fixed

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.2.1.24

Fixed

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.2.1.24

Fixed

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.2.1.24

Fixed

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.2.1.24

Fixed

TCPE-1556

GCSE-3205

The POST /v3/workflows/{workflowId}/jobs endpoint does not update AppInfo, resulting in defective auditlog.

2025.2.1.24

Fixed

TCPE-1560

GCSE-3224

During Alteryx Server upgrades with embedded MongoDB, upgrade errors might not be reported, making the process appear successful despite potential data loss—only visible once users begin using the upgraded Server.

2025.2.1.24

Fixed

TCPE-1564

GCSE-3238

The File Browse tool on Alteryx Server does not process Excel sheets with double-byte characters in the sheet name.

Workaround: Avoid using double-byte characters in sheet names.

2025.2.1.24

Fixed

TCPE-1593

GCSE-3310

In Server UI > Collection > Schedules, the "Next Run" column does not sort correctly when the Profile language is set to Japanese or Chinese.

Workaround: Use English as the language setting, though this might not match all users’ UI preferences.

2025.2.1.24

Fixed

TCPE-1615

GCSE-3356

When a workflow package larger than or equal to 2 GB is uploaded via the Server UI in Admin Console, the UI displays: "The request you are making exceeds the maximum size."

Workaround: An Administrator must check the Server log for details on why the workflow package was not saved.

2025.2.1.24

Fixed

TCPE-1619

GCSE-3373

In Alteryx Server 2025.1.1.27, Interface Tool text labels are truncated due to a CSS property limiting label width to 480px (approximately 85 characters) via the .css-10m2eff class. Disabling this CSS restriction allows labels to display correctly, but no official workaround is currently available.

2025.2.1.24

Fixed

TCPE-1649

GCSE-3400

The base map does not display when accessing the server with SSL enabled.

Workaround: Disable "Globally Enable SSL/TLS" on Alteryx System Settings.

2025.2.1.24

Fixed

TCPE-1673

Designer to Server SAML login via external browser fails when the Web API service is configured to use a custom port.

Workaround: Use the default /gallery root endpoint and set Web API back to the default port.

2025.2.1.24

Fixed

TCPE-1698

GCSE-3545

Transferring ownership of a workflow using a Shared Credential results in the error: “The user supplied does not have access to the given Run As Account.”

Workaround:

  • Option 1: The new owner opens the workflow from Server and resaves it using the shared credential.

  • Option 2: For multiple workflows, update the appInfos.Revisions.0.AuthorId field in MongoDB to match the new owner’s user ID with the following query (replace the user ID with the new owner’s ID):

    db.appInfos.updateMany(
  {"CreatedBy": "NEW_OWNER_USER_ID"},
  {
      $set: {
        "Revisions.0.AuthorId": "NEW_OWNER_USER_ID"
      }
  }
)

2025.2.1.24

Fixed

TCPE-1699

GCSE-3527

The Worker Node starts with an error when the "Use SSL/TLS" option is enabled for the Remote Controller.

Workaround:

  • Associate a certificate with the specified port.

  • Alternatively, you can ignore the error, as workflows will still run successfully on the Worker Node despite the message.

2025.2.1.24

Fixed

TCPE-1702

The "Allow machine to render tiles for mapping" option in Alteryx System Settings is automatically re-enabled after being unticked by the user.

2025.2.1.24

Fixed

TCPE-1704

GCSE-3565

The Drop Down Tool’s default selection name in a Server app does not reflect the setting configured in Designer.

2025.2.1.24

Fixed

TGAL-13091

GCSE-3209

The AS_Schedule.Frequency field is not converted to UTC during the 24.1 update that converts all times to UTC.

2025.2.1.24

Fixed

TGAL-13155

GCSE-3241

Workflows packaged as YXZPs and deployed using the legacy scheduler encounter errors during the scheduling process.

2025.2.1.24

Fixed

TGAL-13226

GCSE-3296

Unable to view Schedules in Designer Desktop Automation after upgrading to version 2025.1.

2025.2.1.24

Fixed

TGAL-13613

.NET Framework upgrade during Server installation fails to upgrade .NET.

2025.2.1.24

Fixed

TPRI-7016

GCSE-2761

License Created Notification is still available in Server UI.

2025.2.1.24

Fixed

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.2.1.24

Fixed

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 when using SQL Server persistence.

2025.2.1.24

Fixed

TPRI-8482

GCSE-3019

Alteryx Server Schedule Forecast does not display Saturday schedules for users in time zones far west of UTC, or Sunday schedules for users far east of UTC.

2025.2.1.24

Fixed

TPRI-8564

District icon is not displaying after edit.

2025.2.1.24

Fixed

TPRI-9058

Clicking on links generated from published or draft pages results in a "Page Not Found" error.

2025.2.1.24

Fixed

Known Issues

Known

Major Release Version 2025.2.1.24

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.

Workaround: Once reindexing is performed, the workflows are visible with the global search.

2025.2.1.24

Known

TCPE-1642

GCSE-3206

Intermittent failures occur when running workflows that use the SharePoint Input tool in Alteryx Server.

2025.2.1.24

Known

TCPE-1705

GCSE-3568

The Workflow Migration Utility publishes multiple copies of a workflow during migration.

Workaround: Edit LoggingDB.sqlite to remove old records containing the Source and Target workflow IDs, keeping only the most recent record.

2025.2.1.24

Known

TCPE-1714

GCSE-3593

Errors occur when accessing results or outputs from SQL Server via Desktop Automation in Designer.

Workaround: Ensure Designer is licensed with both Designer and Desktop Automation, or a Server license. The workaround will not work if only a Designer license is present.

In Designer, go to Options > Advanced Options > System Settings, click through without changing settings, and finish. Restart Designer. If the issue persists, close Designer, delete or rename %ProgramData%\Alteryx\RuntimeSettings.xml, reopen Designer, and repeat the steps above.

2025.2.1.24

Known

TCPE-1715

GCSE-3598

The Render tool cannot write files to a UNC path if any directory in the path contains a space-hyphen-space (" - "). This issue is commonly encountered with folders mapped via OneDrive for SharePoint syncing.

Workaround: Rename the folder to remove the " - " from the directory name or use the latest SharePoint connector.

2025.2.1.24

Known

TCPE-1727

GCSE-3615

Multiple workflow versions falling out of sync can cause issues with workflow deletion, disabled schedules, and loading the schedule page.

2025.2.1.24

Known

TCPE-1736

GCSE-3652

The Drop Down tool does not populate the drop-down list in the Server UI.

2025.2.1.24

Known

TCPE-1738

GCSE-3661

In a series of at least three chained analytic apps, the last app fails to read the output file from the first app.

Workaround: Configure the second-to-last app (App 2) to explicitly write the output file from App 1 (for example, "app1output.yxdb") to the temporary staging location using a relative file path.

2025.2.1.24

Known

TCPE-1742

GCSE-3665

In environments with many schedules, the Admin > Workflows > Bulk Transfer Owner UI might hang or take several minutes to load, and a 504 Timeout error may appear in HAR logs.

Workaround: Change ownership individually from the Admin > Workflows > [Specific Workflow] Details page.

2025.2.1.24

Known

TCPE-1744

GCSE-3670

The Alteryx Server Usage Report MongoDB_Schema_23.2.json file uses the wrong schema for Server version 2024.1 and newer.

2025.2.1.24

Known

TCPE-1746

GCSE-3682

The SQL Migration Workflow does not use the correct schema.

Workaround: Before running the SQL Migration Workflow, add an “s” to the end of the following table names: alteryx_server.CollectionOwnerChangedFromNotification and alteryx_server.CollectionOwnerChangedToNotification. Once the workflow is complete, remove the added “s” from the table names.

2025.2.1.24

Known

TCPE-1752

GCSE-3692

Unable to upload a workflow using the POST /v3/workflows API when using a CredentialID that is shared via a Custom Group, which is shared with an AD Group.

Workaround: Open the required credential and add the user directly under the Users tab.

2025.2.1.24

Known

TCPE-1756

GCSE-3705

SCIM does not remove deleted users from their associated custom groups.

Workaround: Identify all deleted users in the database, check if they are still associated with any UserGroups, and manually remove those users from all associated groups in MongoDB.

2025.2.1.24

Known

TCPE-1761

GCSE-3713

With SSL-enabled Server, Alteryx SAML requests ignore ACS BASE URL case sensitivity, which can cause issues with case-sensitive identity providers (IdPs).

Workaround: Ask the IdP to use lowercase for both the Entity ID and ACS URL, and update Alteryx System Settings to match this format for compatibility.

2025.2.1.24

Known

TCPE-1763

GCSE-3723

When migrating from MongoDB to SQL Server with WinAuth DB, clicking on a collection name results in a Collection Not Found error.

2025.2.1.24

Known

TCPE-1764

GCSE-3722

Duplicate schedule Creation on click.

2025.2.1.24

Known

TCPE-1765

GCSE-3729

Unable to delete users via the DELETE v3/users endpoint in a Server environment with a user-managed SQL database.

Workaround: Set user to inactive/no access from front end.

2025.2.1.24

Known

TCPE-1766

GCSE-3736

When migrating a Server environment from MongoDB to SQL that is configured with SCIM, the SCIM token is not migrated to SQL.

Workaround:

  1. Start the previous MongoDB instance separately.

  2. Access the AlteryxGallery.Configuration.ScimConfiguration object from the previous MongoDB instance and save its values.

  3. Replace the highlighted values within the VALUES parameters in the proper order using the following SQL command based on the values obtained in step 2:

    INSERT INTO [AlteryxGallery].[alteryx_server].[ScimTokens] ([Id], [Jwt], [LifetimeDays], [SymmetricKey])
VALUES ('ScimConfigurations.Id', 'jwt', lifeTime (numeric), 'SymmetricKey');

  4. Run the SQL query to populate the token value.

  5. Re-test using Postman to confirm the fix (a service restart might be required).

2025.2.1.24

Known

TCPE-1769

GCSE-3742

Public workflow notifications are being sent even when the notification toggle is turned off.

Workaround: Create a notification group (for example, “Workflow shared in public Server”) that includes all active user profiles, and manually disable email notifications for this group.

2025.2.1.24

Known

TCPE-1775

GCSE-3711

When a Macro embedded in an Analytic App workflow is configured to pull all sheets from a file via the file browser, it works in Designer and app testing, but running it on Server results in an error: Record #1: Tool #1: [List of Sheet Names] 'GL Prov$' does not match a sheet or named range in the selected Excel file, or the file is corrupted.

Workaround: In the workflow, replace the File Browse tool with the Text Box tool in the app interface.

2025.2.1.24

Known

TCPE-1777

GCSE-3759

Curators who have user Role=Default and are part of Custom User Group with Role=Curator can’t change the ownership of a Collection.

  • Workaround 1: Directly set the user’s Role=Curator. Go to Admin > Users.

  • Workaround 2: Use the Swagger API.

  • Workaround 3: Create an Analytic App using the Server API Tool that can be shared in a Collection accessible only to the IIT_Curators group. The app should prompt for the Collection ID and New Owner User ID, then call the API to change ownership, using one of the Curator’s API Key and Secret for authentication. Collection and User IDs can be found by viewing them and copying the ID from the end of the URL. This approach avoids direct changes to Curator roles, keeping Admins managed via the IIT_Curators group.

2025.2.1.24

Known

TCPE-1779

GCSE-3771

After upgrading to Alteryx Server 2025.1 (Patch 2), users encounter multiple issues when using the PDF To Text tool, particularly when processing PDFs created by ChatGPT.

Workaround: Use Microsoft Word (or another standard PDF generator) to create the PDF file before processing it through the PDF To Text tool.

2025.2.1.24

Known

TCPE-1786

GCSE-3793

Alteryx Server 2024.2.1.193: Encountering issues while adding an Image URL to a District.

2025.2.1.24

Known

TDCE-929

GCSE-3720

Intermittent errors occur when running workflows on Alteryx Server that use OLE DB or ODBC drivers to connect to Azure Synapse serverless SQL pools.

Workaround (if applicable): Run query during less busy period for Alteryx Server.

2025.2.1.24

Impeded

TGAL-13849

GCSE-1787

When an Analytic App runs in Server UI (21.4.2.47895+), the File Browse tool passes an incorrect file path to the Macro Control Parameter.

Workaround: Replace File Browse tool with Text Box tool in the App interface.

2025.2.1.24

Known

Security Updates

Major Release

Version: 2025.2.1.24

Major Release Version 2025.2.1.24

ID

Description

Version

Issue Status

TGAL-13310

A Stored Cross-Site Scripting vulnerability was resolved.

2025.2.1.24

Fixed

TGAL-14015

A critical Server vulnerability allows non-administrative users to access credential identifiers from workflows they can view, including those tied to higher-privilege accounts. The system fails to properly validate whether a user is permitted to use a given credential, enabling unauthorized workflow execution and potential privilege escalation.

Credit: Alexander Malakhov and Alex Gross – Siemens Energy

2025.2.1.24

Fixed

GVM-6520

SQLite Components were upgraded to version 3.50.4 to address CVE-2025-6965.

2025.2.1.24

Fixed

In this section: