Skip to main content

Server 2023.2 Release Notes

Release Note Product Versions

Version 

Release Date 

Release 

End of Support 

2023.2.1.7

November 1, 2023

Major

November 1, 2025

2023.2.1.51 (Patch 1)

December 8, 2023

Minor

November 1, 2025

2023.2.1.89 (Patch 2)

January 25, 2024

Minor

November 1, 2025

Upgrade Considerations

Before you upgrade to 2023.2, please note: 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. This will be fixed in an early 23.2 patch, but for the moment, please follow the workaround instructions in this article.

Upcoming Deprecation of Insights

We will be deprecating insights in an upcoming release.

How to Solve Migration Failures

If a failure occurs during the migration, the service won’t start. In such a case, please check the logs, fix the data, and then start the service again.

Migration failures are logged in 2 places:

  • AlteryxServiceLogs: The default location is C:\ProgramData\Alteryx\Service\Logs. These logs will point out to the MigrationLogs.

  • MigrationLogs: The default location is C:\ProgramData\Alteryx\Gallery\Logs.

Both of these log file locations can be changed in Alteryx System Settings.

Required Password Reset for Built-In Authentication

If you use built-in authentication and you upgrade from a version lower than 2022.1, you need to reset your password due to security improvements. If you didn't reset your password in version 2022.1, you need to have SMTP enabled. This is so users can reset their password via the forgot password functionality or so that an admin can trigger password resets for all users via the UI or API. For more information on how to reset your Server password after an upgrade to 2022.1, visit the Reset a User's Server Password help page.

Important

The Alteryx Server version 2023.2 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 2023.2 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

CLI Option to Connect to Remote Controller

As an administrator, you can now securely transfer encryption keys from your existing environment to migrate Server to a new host or mitigate an outage.

For more information, go to Encryption Key Transfer Process.

New CLI Command

As an administrator, you can now use the new CLI command:

  • setmongoconnectionserver: Sets the MongoDB connection string for the Server UI connection.

Additionally, we’ve added the following commands to our documentation:

  • setmongoconnectionworker: Sets the MongoDB connection string for a Worker.

  • setmongoconnectioncontroller: Sets the MongoDB connection string for a Controller.

For more information, go to AlteryxService Commands.

Swagger V3 API Documentation Update

Updated and improved our Swagger documentation to help you better use and understand all Server V3 APIs. We’ve made updates to endpoint and ID descriptions, implementation notes, and URLs. For more information about endpoints, go to our Server API Documentation.

SQL __ServiceData Blob Removed

Removed __ServiceData Blob to allow better search and sort functionality for certain sets of data. The changes that have occurred in MongoDB due to the removal of the blob are as follows:

  • Columns that were previously hidden in the Blob are now available to be queried.

  • All columns are now of the appropriate type (instead of all being stored as strings), making our Server more consistent with Mongo DB.

  • It also brings performance improvement and and increases flexibility for certain queries. For example, you can perform natural datetime comparison queries on datetime columns.

We’ve removed the Service Blob for both FIPS and non-FIPS versions of Server. The changes are reflected on our AlteryxService MongoDB Schema help page.

Upgrade Embedded MongoDB to Supported Version

This feature targets to upgrade our embedded version of MongoDB to version 6. Please follow the below steps in order to upgrade to MongoDB version 6:

  1. Download Alteryx Server 2023.2 from downloads.alteryx.com.

  2. Run the installer.

  3. You get a prompt to upgrade your MongoDB.

  4. Once MongoDB has been migrated to the latest version and Server is installed successfully, you can run Alteryx Server as usual.

  5. In case of failure during the migration of MongoDB, you will be prompted to contact customer support.

  6. If the migration fails, or if you need to rollback to a previous version, you can manually uninstall 2023.2 and restore a backup. For more information, please visit the Downgrade Alteryx Server help page.

Note

Please note that during the upgrade process, there will be no option to install Predictive Tools in the installer wizard since we have prioritized the MongoDB migration to take precedence. If you would like to install Predictive Tools, please follow these steps:

  1. Go to this file location: <Alteryx_Install_Path>\RInstaller.

  2. Run the RInstaller file for your version. For example, RInstaller_2023.2.1.7.exe.

  3. Start the Alteryx Service if it's not running.

Note

  • When upgrading from Server versions between 2022.1 and 2023.1, MongoDB will upgrade to version 6 as part of the installation using steps above.

  • When upgrading from Server version 2021.4 to 2023.2, MongoDB will upgrade to version 6 as part of the installation using the steps above. In this instance, if you use built-in authentication, users will need to reset their password due to improvements in security. For more information how to reset your Server password after upgrade to 2023.2, visit the Reset a User's Server Password help page.

  • When upgrading from Server versions between 2019.3 and 2021.3, you will need to upgrade to a Server version (2021.4 and above) which uses MongoDB version 4.2 first and then you can upgrade to version 2023.2 which uses MongoDB version 6.

  • When upgrading from Server versions older than 2019.2, you will need to upgrade to a Server version (2019.3 to 2021.3) which uses MongoDB version 4 first and then upgrade to a version (2021.4 and above) which uses MongoDB 4.2 and then finally can upgrade to version 2023.2 which uses MongoDB version 6.

Timezone for Schedules in Server API V3

Added timezone for the following API V3 endpoints:

  • POST /v3/schedules: This endpoint has been updated to allow you to set the time and timezone for schedules.

    For example, if you want to set a schedule for 5:00 PM Mountain Time, you should be able to set the schedule to 5:00 PM and select Mountain Time as the timezone. The timezone option is optional, and if you don’t specify the timezone, the default timezone will be UTC time.

  • PUT /v3/schedules: This endpoint has been updated to allow you to update existing schedules created using the API and add a timezone selection if you choose. 

    For example, if you created a schedule using the API endpoints and the time had to be set in UTC, you should be able to update the schedule and change the time and timezone.

    However, existing schedules will continue to run as expected if you choose not to add a timezone.

  • GET /v3/schedules/{id}: This endpoint has been updated you can view the timezone for an existing schedule filtered by Id.

  • GET /v3/schedules: This endpoint has been updated so you can view the timezones for all the existing schedules.

For more information about the endpoints, access the Swagger documentation by selecting the question mark icon in the upper right corner of the Server interface. For valid timezones to use in the above API endpoints, see the Schedules Endpoints help page.

New DCME API V3 Endpoints

Added new DCME API V3 endpoints. The DCME endpoints are divided into 2 groups: DCME endpoints that can be used by users with API access, and DCME Admins endpoints for Curators with API access.

  • As a user, you can use these endpoints to retrieve information about your DCM connection records, share a DCM connections with specified users and groups, create, update, delete, and unshare a DCM connection.

  • As an admin, you can use the admin endpoints to manage all DCM objects in your environment.

For more information, go to DCME Endpoints and Server API V3.

Server V3 API: Allow Users To Run a Job Shared via Collections

This API allows users to run workflows that have been shared with them via a collection. We’ve removed any subscription permission limitations. A user or an admin is not limited to use any API based on the subscription they are in, but being in the same subscription as a workflow can grant them access to run these API endpoints.

Users and admins are now able to use this API endpoint on any workflows they have access to either by owning the workflow, having the workflow shared with them via a collection, or being in the same studio.

Synchronization in Data Connection Manager (DCM) between Alteryx Designer and Alteryx Server

Added the Server Synchronization settings for DCM in Alteryx System Settings. Now it provides admins with the flexibility to manage the flow of connections between the Designer and Server environments. You can choose between Full synchronization, One-way to Designer, and No synchronization. For more information about the settings, go to DCM - Server and Data Connection Manager: Server UI.

Options for Sharing Connections of a Data Source

When sharing a connection, you can now select from 2 options how to share this data source: Share for Collaboration and Share to Run on Server Only.

  • Share for Collaboration: Share a connection allowing multiple users to collaborate on creating workflows. This form of sharing allows other users to synchronize the connection to their Designers to build workflows using this connection.

    • The connection owner can choose to share their credentials together with the connections. If they choose to, other users won’t be able to view the secrets but will be able to use them in workflows. Other users won’t be able to re-use the shared credentials in any other connection - it will be bound to the shared connection only. If the connection owner decides to not share the credentials, each user will then be required to connect their own credentials—for the same authentication method—in order to use the connection.

    • No updates in workflows are necessary to execute the workflow by other users who have this connection shared.

    • Only Server Curators are allowed to share connections for Collaboration.

  • Share to Run on Server Only: Share a connection for workflow execution on Server. The user can’t see the connection, nor can they synchronize it and use it in Designer.

For more information, visit the Data Connection Manager: Server UI help page.

Windows Server 2012 End of Support

As of Server version 2023.2, Alteryx no longer supports Windows Server 2012 as it has reached the end of support by Microsoft. Go to Windows Server 2012 and 2012 R2 reaching end of support to learn more.

Fixed and Known Issues

Fixed

Major Release Version 2023.2.1.7

ID 

Description 

Version 

Issue Status 

TCPE-592

GCSE-1150

When edited, Monthly Recurring Schedule changes from Day of Month to On the X of the Month.

2023.2.1.7

Fixed

TCPE-597

GCSE-1178

Exception is thrown when asserting SAML response from IDP (when using Meta or x509).

2023.2.1.7

Fixed

TCPE-605

GCSE-1189

If a user creates a schedule with only a space character, the schedule becomes inaccessible from the web interface.

2023.2.1.7

Fixed

TCPE-632

GCSE-1233

Server Web API V1 endpoint GET admin/v1/{appID}/package/ returns corrupt file when downloading a Chained App as a .yxzp package.

2023.2.1.7

Fixed

TCPE-678

GCSE-1349

Unable to create or view schedules that use the 'Asia/Manila +08:00' time zone if the Windows time zone on the Server machine is set to a time zone behind UTC (for example, UTC-1, UTC-2, etc.).

2023.2.1.7

Fixed

TCPE-685

GCSE-1362

When upgrading to 2022.3 (from 2021.4), there is no longer a "None specified" option under Default Workflow Credentials for the settings of a Studio.

2023.2.1.7

Fixed

TCPE-691

GCSE-1384

Running workflows from the Version window is not possible if the workflow was saved to specify credentials. The pop up window to specify credentials doesn’t appear.

2023.2.1.7

Fixed

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.

2023.2.1.7

Fixed

TCPE-737

GCSE-1487

The GET /v1/jobs/{id}/output/{outputId} endpoint intermittently fails with response code 0.

2023.2.1.7

Fixed

TCPE-779

GCSE-1515

Unable to schedule Server workflows using Legacy scheduler in Designer 2023.1

2023.2.1.7

Fixed

TGAL-7677

Global search fails if the workflow / insight / districts / collection name contains special characters.

2023.2.1.7

Fixed

TGAL-7708

The "in beta" text in the notification about 7 language support has to be removed.

2023.2.1.7

Fixed

TGAL-7709

Update copy/text in System Settings > Engine > General > Run engine at a lower priority.

2023.2.1.7

Fixed

TGAL-7825

Insights might not render in multi-node environments and display the message "Error rendering insight. If this problem persists, please contact your Systems Administrator." To work around this issue, please ensure the Insights worker is enabled on your controller.

2023.2.1.7

Fixed

TGAL-7846

When Administrators upload workflows using the "+New" button in the Admin UI, workflows are not being validated as they were in previous versions of Server.

2023.2.1.7

Fixed

TGAL-7851

Alteryx Server public endpoint /admin/v1/workflows/jobs only returns a maximum of 15 jobs. The endpoint should be capable of returning a job for each workflow without limit.

2023.2.1.7

Fixed

TGAL-7868

Global search issues: When you search with a full name, the search doesn't match any records. When you search for a workflow / insight / collection that contains special characters, the results don't match either. The term is passed through the Sanitize function unnecessarily.

2023.2.1.7

Fixed

TGAL-7926

Pagination is not working as expected for these modules: Admin (Workflows, Users, Subscription, Tags, and Pages), Home (Districts and Workflows).

2023.2.1.7

Fixed

TGAL-8049

GCSE-1059

API calls to Admin V1 API are intermittently failing.

2023.2.1.7

Fixed

TGAL-8705

GCSE-1663

In Designer, collection owners are unable to see the workflows added by other users.

2023.2.1.7

Fixed

TGAL-8792

If the wrong key is in place after upgrade to Crypto library 2.0, an error 'AlteryxService_InitLocalEncryptedStorage_Error' appears.

2023.2.1.7

Fixed

TPRI-1298

View in Browser functionality is breaking from Designer after saving the workflow to Server. Token based authentication issue.

2023.2.1.7

Fixed

TPRI-1320

Admin Jobs page is empty with no tabs.

2023.2.1.7

Fixed

TPRI-1329

GCSE-1228

Unable to access DCM connection on the Server through DCM tool (interface tool). The Snowflake Simba connections are not listed when published on Server.

2023.2.1.7

Fixed

TPRI-1492

App Re-Run button appears on all Job Runs instead of the latest job run.

2023.2.1.7

Fixed

TPRI-1575

GCSE-1302

System messages do not appear when first logging in to Server.

2023.2.1.7

Fixed

TPRI-1590

Getting wrong occurrence after editing the schedule for a recurring schedule at a monthly frequency.

2023.2.1.7

Fixed

TPRI-1706

GCSE-1386

Server UI site logo is truncated after upgrade to 2023.1.

2023.2.1.7

Fixed

TPRI-1710

In analytic apps, two groups of radio buttons are being treated as one group on Server.

2023.2.1.7

Fixed

TPRI-1797

Data Connections Admin Screen is missing an 's' in Connection in the title of the page.

2023.2.1.7

Fixed

TPRI-1825

Nested radio button is failing to retain the user selected values in an analytic app while re-run.

2023.2.1.7

Fixed

TPRI-1882

GCSE-1431

The File browse feature doesn't retain its value on Re-Run if the condition 'Enable/Disable Containers from Condition' is set.

2023.2.1.7

Fixed

TPRI-1927

GCSE-1429

After upgrading from 2022.1 to 2023.1, the Tree Interface tool is not working when running in a chained app.

2023.2.1.7

Fixed

TPRI-1976

TCPE-720

When running an analytic app with "Generate field map" enabled in File Browse Tool and "Output File Name as Field" selected in Input Data Tool, it provides different UI in Designer and in Server.

2023.2.1.7

Fixed

TPRI-2018

GCSE-1467

Tree Interface tool doesn't display all custom XML in Gallery 2023.1

2023.2.1.7

Fixed

TPRI-2019

GCSE-1469

Hide Control option within a Text Box Interface tool doesn't work when run in Gallery 2023.1

2023.2.1.7

Fixed

TPRI-2020

GCSE-1450

When using a File Browse Tool with Field Mapping setup, the field mapping options will not be displayed in the Server UI.

2023.2.1.7

Fixed

TPRI-2043

GCSE-1437

Drop Down and List Box Tools return NAME from NAME:VALUE pair rather than VALUE.

2023.2.1.7

Fixed

TPRI-2045

Type column filter in Admin > Users > Groups displays ActiveDirectory instead of Active Directory.

2023.2.1.7

Fixed

TPRI-2080

When using the Re-Run button after running an analytic app in Server UI, the NULL values that were previously selected are not retained in the Interface tool textbox.

2023.2.1.7

Fixed

TPRI-2120

When you select an Excel file with multiple sheets and select one sheet to get the output, the workflow crashes.

2023.2.1.7

Fixed

TPRI-2128

When using the Re-Run or back button after running an analytic app (with Tree tool interface) in Server UI, the values that were entered are not retained in the Tree tool.

2023.2.1.7

Fixed

TPRI-2233

Re-run: File Browse issue with Field Mapping option: Different UI in Designer versus Gallery for specific tool configuration.

2023.2.1.7

Fixed

TPRI-2273

Users can’t copy the text from the messages of the Job Results.

2023.2.1.7

Fixed

TPRI-2297

On the admin and user schedules pages, when trying to filter by status, the filter is not working unless choosing “Select All” or when no option is selected.

2023.2.1.7

Fixed

TPRI-2411

GCSE-1438

Analytical App Date tool: When you choose a date, it picks the previous day.

2023.2.1.7

Fixed

TPRI-2444

GCSE-1519

File Browser Tool: When using File Input, there is a noticeable delay in the Table/Sheet selection prompt without any indication that a large XLSX file is loading in the background.

2023.2.1.7

Fixed

TPRI-2493

GCSE-1524

File Browse in Server with a list of sheets selected outputs the first sheet, not sheet names.

2023.2.1.7

Fixed

TPRI-2631

GCSE-1485

Diagnostics Page is unable to show more than 7 Worker nodes on a single screen.

2023.2.1.7

Fixed

TPRI-2635

GCSE-1538

AMP indicator not working for jobs results.

2023.2.1.7

Fixed

TPRI-2636

GCSE-1541

Server UI does not display the expected preview of the file extension PCXML when used with the Frequency Table Tool.

2023.2.1.7

Fixed

TPRI-2807

GCSE-1555

When adding an URL to the metadata of a workflow, it is getting prefixed by the app URL.

2023.2.1.7

Fixed

TPRI-2820

Re-run isn't retaining for List Box analytical app when "All checked by default" option is selected.

2023.2.1.7

Fixed

TPRI-2887

When running an analytic app, the DCM tool is giving Null as output for default value.

2023.2.1.7

Fixed

TPRI-2945

Default dropdown value set for dropdown Interface tool is not working in Server.

2023.2.1.7

Fixed

TPRI-3012

The Cancel button functionality is not retaining the original values for the Single selection Tree tool before running the app for the first time.

2023.2.1.7

Fixed

TPRI-3057

Analytic App with DCM Connection tool doesn't display the Connection ID in output on run and re-run.

2023.2.1.7

Fixed

TPRI-3211

Post Onyx: Issue with editing the workflow and adding tags.

2023.2.1.7

Fixed

TPRI-3240

Post Onyx SAML and WinAuth: File browse is failed to retain the values on re-run when standard database file formats are enabled in configuration.

2023.2.1.7

Fixed

TPRI-3273

Output of the dropdown Interface tool with default dropdown value is giving wrong output.

2023.2.1.7

Fixed

TPRI-3283

GCSE-1651

When running an analytic app, the job status message under Output Preview and the green status pop-up display conflict.

2023.2.1.7

Fixed

TPRI-3321

GCSE-1666

File Browse Tool: Unable to configure analytic app in Server if File Browse Tool sits outside of app interface Group Box.

2023.2.1.7

Fixed

TPRI-3349

When running an analytic app, edited values in a nested checkbox are not retaining their values when selected.

2023.2.1.7

Fixed

TPRI-3469

GCSE-1665

When scrolling down in a section or workflow and then selecting another page, the page stays scrolled down and doesn't return to the top of the page.

2023.2.1.7

Fixed

Fixed

Minor Release Version 2023.2.1.51

ID

Description

Version

Issue Status

TGAL-9017

Error: "Failed to retrieve Mongo connection information <Server Error: 404> after Installing Alteryx Server 2023.2 with User-Managed MongoDB.

2023.2.1.51

Fixed

Fixed

Minor Release Version 2023.2.1.89

ID

Description

Version

Issue Status

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.

2023.2.1.89

Fixed

TPRI-4100

GCSE-1822

Chained applications require manual run for each analytics app even if the app does not require any user input.

2023.2.1.89

Fixed

Known

Major Release Version 2023.2.1.7

ID 

Description 

Version 

Issue Status 

TCPE-771

GCSE-1547

The PUT /v3/schedules/{id} endpoint returns 500 error.

2023.2.1.7

Known

TCPE-785

GCSE-1570

Scheduled jobs are not visible in Server Admin interface > Schedule Forecast. The page loads but schedules past a certain date do not appear on the forecast.

2023.2.1.7

Known

TCPE-796

Workflow with File Browse Tool fails in Server when the File Browse Tool tries to read the large XLSX file as the data source.

2023.2.1.7

Known

TCPE-808

GCSE-1604

In Server UI, Workflow Version History incorrectly shows older Designer version after workflow is initially resaved with newer Designer version.

2023.2.1.7

Known

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

2023.2.1.7

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.

2023.2.1.7

Known

TCPE-822

GCSE-1628

For Server 2023.1, when a new user is prompted to select a time zone and selects Save, nothing appears to happen. This occurs for Service accounts that do not have a first or last name.

2023.2.1.7

Known

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.

2023.2.1.7

Known

TCPE-845

GCSE-1713

When the "Alteryx Database as Browse Everywhere" file type is chosen, the output is created as YXDB file instead of YXBE file.

2023.2.1.7

Known

TCPE-858

GCSE-1759

The DELETE /v3/workflows/ API endpoint fails for all workflows with 500 Error if a workflow associated with the schedule is deleted from the Server UI.

2023.2.1.7

Known

TGAL-8244

Admin Jobs Count is showing inconsistently.

2023.2.1.7

Known

TGAL-8263

GCSE-1184

API V3: Schedule PUT API allows the priority to be changed when the user profile does not have access.

2023.2.1.7

Known

TGAL-8602

When using the put/v3/schedules/{scheduleid} endpoint, endTime is not showing according to given time zone properly in Response Body.

2023.2.1.7

Known

TGAL-8689

A new user with Curator role is not able to run the public workflow through public API V1 and V2 job endpoints.

2023.2.1.7

Known

TGAL-8841

GCSE-1622

Excel file output appears to be corrupt when retrieved from Server API call GET /v1/jobs/{id}/output/{outputId}.

2023.2.1.7

Known

TGAL-8893

TPRI-3813

The Sorting on Name and Workflow column on Schedules page is not working according to the alphabetical or numerical order and likely to be sorting on basis of a Workflow ID.

2023.2.1.7

Known

TPRI-3162

Issue with creating or editing a notification group where all notifications have already been added.

2023.2.1.7

Known

TPRI-3662

GCSE-1758

In the File Browse Tool, when you are mapping fields to an app, this is not as clear as on previous Server versions. In previous versions, the selected fields were grayed out.

2023.2.1.7

Known

TPRI-3820

TGAL-8887

Users are unable to update tags after assigning max number of (5) tags.

2023.2.1.7

Known

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.

2023.2.1.7

Known

Security Updates

Fixed

Patch/Minor Release Version 2023.2.1.89

ID

Description

Version

Issue Status

TBO-1141

Updated embedded OpenSSL versions to 3.0.12 (Engine, AMP) and 1.1.1w (v1 SDK). Addresses the following CVEs:

  • cve-2023-5363

  • cve-2023-4807

  • cve-2023-3817

  • cve-2023-3446

  • cve-2023-2975

  • cve-2023-2650

  • cve-2023-1255

  • cve-2023-0466

  • cve-2023-0465

  • cve-2023-0464

  • cve-2022-3996

Go to www.openssl.org/news/openssl-3.0-notes.html and www.openssl.org/news/openssl-1.1.1-notes.html.

Note: Alteryx Server relies upon the native Windows SChannel implementation for inbound TLS/HTTPS and TLS Service Layer communications. In a networking context, OpenSSL is used only in 1) outbound connections occurring as a result of Engine/AMP/SDK-tool execution during workflow runs, and 2) outbound connections to http://alteryx.com and http://flexnetoperations.com for licensing. activation, and telemetry.

2023.2.1.89

Fixed