Server Release Notes

What's New in Server

Version: 2025.2.1.24
Release Date: December 3, 2025

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.

Original source Report a problem

What's New in Server

Version: 2025.1.1.27
Release Date: May 13, 2025

Go to the complete Server 2025.1 Release Notes.

New Features

Auditing Configuration Changes in System Settings

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.

Workflow Results View for Admins

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.

New Credentials Page for Non-Admin Users

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.

Inviting Users to Manage Credentials for Admins

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 information, see Invite to Create or Edit a Credential.

Server API

New Endpoint to Cancel a Specific Job

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.

New API Endpoints for Server Credentials

We've added two API credential endpoints for Server credentials (non-DCM):

• Create Server credentials: POST /v3/credentials
• Update 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.

Cron Expression Support for Schedule Endpoints

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/schedules
• PUT /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:

1. 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 * *
2. Five-Field Cron format only.
   This implementation supports only the five-field Cron format:
   minute hour day-of-month month day-of-week
3. Step values are not supported in the day-of-week (last) field.
   Invalid expression: 0 * * * */tue
   Valid expression: 0 * * * TUE
   For more details, visit the Schedule Endpoints help page.

Server Usage Endpoints

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 One Platform at regular intervals. Admins can review this data directly in Alteryx One.
• Offline customers: Offline customers must use Alteryx One for licensing and billing. The usage data report will not be automatically sent to Alteryx One. However, you can manually extract and upload the report via the API endpoints available on Server and Alteryx One.
  For detailed steps on extracting and loading usage data to Server, please refer to Server Usage Endpoints.

Added SAML Assertion Encryption Support

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.

Original source Report a problem