What's New in Server
Version: 2025.2.1.24
Release Date: December 3, 2025
Go to the complete Server 2025.2 Release Notes
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/workflowsPOST /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.