Server 2024.2 Release Notes
Release Note Product Versions | |||
|---|---|---|---|
Version | Release Date | Release | End of Support |
2024.2.1.14 | October 30, 2024 | Major | October 30, 2026 |
2024.2.1.41 (Minor) 2024.2.1.1.41 (Patch 1) | December 5, 2024 | Minor | October 30, 2026 |
Upgrade Considerations
Warning
This section contains important updates regarding the 2024.2 release. Please review these items before you upgrade.
Upgrade Embedded MongoDB to Version 7
As part of Server 2024.2 installation, you need to upgrade the embedded MongoDB to version 7. Please follow the steps below in order to upgrade:
Download Alteryx Server 2024.2 from downloads.alteryx.com.
Run the installer.
MongoDB will be automatically upgraded to version 7 and you will get the following message:
Once MongoDB has been migrated to the latest version and Server is installed successfully, you can run Alteryx Server as usual.
In case of failure during the migration of MongoDB, you will be prompted to contact Customer Support.
If the migration fails or if you need to rollback to a previous version, you can manually uninstall 2024.2 and restore a backup. For more information, go to the Downgrade Alteryx Server help page.
Warning
When you upgrade from Server versions older than 2023.2, you need to first upgrade to a Server version which uses MongoDB version 6 (2023.2 or 2024.1), and then you can upgrade to version 2024.2, which uses MongoDB version 7. Failure to do so will result in an error message and the migration will fail.
Localization
The 2024.2 release might have localization issues. While all supported languages are operational, some new features might not perform as expected, and you might notice translation inaccuracies or inconsistencies. We expect significant improvements in the upcoming 2025.1 release.
Alteryx Server-FIPS
The Alteryx Server version 2024.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 2024.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
UI Filter and Sort for Workflows, Schedules, and Jobs
We improved our searching and sorting capabilities on Server for both admin and non-admin users, enhancing the overall experience of the Server UI. Now you can do the following with ease:
Filter by AMP or E1 on the Schedules page and My Workspace (My Files, Shared With Me, Public).
We’ve added an Engine column to Admin homepage > Jobs where you can filter by AMP or E1.
We’ve enabled Type field sorting in Server UI > My Workspace (My files , Shared With Me, Public), and on Admin homepage > Workflows.
We’ve added Engine filter on Admin homepage > Workflows (Private, Public, All).
For more information, go to Search for Assets.
Display Recent Workflows in the Add Workflow Dropdown
When you add a workflow to a collection, you will now see a list of your most recently uploaded workflows in the "Add Workflow" dropdown menu.
When you open the "Add Workflow" pop-up, a drop-down menu appears showing the 10 most recent workflows until you start typing in the search bar.
The workflows are sorted based on the last uploaded date, ensuring that the most recent and relevant workflows are easily accessible.
For more information, go to Add Workflows to a Collection.
File Browse Improvement in Analytic Apps
If you upload an XLSX file larger than 200 MB via the File Browse tool in Analytic Apps, it might cause performance and loading issues. The following message will be displayed to inform you of potential performance issues: Large file sizes are more likely to experience performance/loading issues in Server when using File Browse. This might cause the application to error.
Ability to Resize the System Settings Window
We enhanced the System Settings window. You can now use the following resizing options:
Easily maximize the System Settings window to full screen or minimize it to the taskbar using the newly added buttons located at the top right corner of the window.
Adjust the size of the System Settings window by dragging the edges or corners with the resizing arrows.
For a more user-friendly experience, we have optimized the initial behavior of the System Settings window. The first time you open System Settings, it will automatically open at a size that fits your screen perfectly and will be centered on your screen. No buttons will be hidden.
New Admin Settings: Timeout to Cancel Jobs
We added new options in Server Settings: Cancel Scheduled Jobs Running Longer Than and Cancel Manual Jobs Running Longer Than. As an admin, you can specify timeout values after which scheduled and manual run jobs should get canceled. To do so, go to Admin > Settings > Assets.
We enabled the System Settings for manual run jobs as well. Previously, it was allowed only for scheduled jobs. Now, these added admin settings are applied at system level. We continue to have the timeout values in System Settings (under Worker > General > Cancel jobs running longer than (seconds)) which is useful in a multi-node environment. If a timeout value has been configured on the Server UI, this will be set across all workers. However, if a timeout value has been set on the System Settings on a particular worker, this will override the UI values.
For more information, go to Alteryx Server Settings and Worker.
Migrate Data Connections and Workflows to DCM
To simplify the shift from Data Connections to DCM Connections, starting with the Server 2024.2 release it is possible to migrate all Data Connections and respective workflows to be replaced by DCM Connections. First, it is necessary to migrate each data connection and then trigger the migration of workflows. Checking our Maveryx Community blog post How to migrate Server Data Connections to DCM might help you understand the journey better.
For more information, go to Data Connections.
Server API Updates
New API Endpoints for Subscriptions (Studios)
We've given admins the ability to manage studios using Server V3 API endpoints. These APIs will help you edit studios in bulk and provide you with the ability to move individual users back to individual studios.
GET /v3/subscriptions: This API endpoint enables to retrieve all subscription records. As an admin, you will be able to fetch the data based on optional input parameters such as subscription name, shared schedules enabled (true or false), default workflow credential ID, number of workflows, and number of users.GET /v3/subscriptions/{subscriptionId}: This API will help admins to look for an existing subscription. To search for a subscription, you need a subscription ID.DELETE /v3/subscriptions/{subscriptionId}: As an admin, you can now delete subscriptions using theDELETE /v3/subscriptions/{subscriptionId}API endpoint.PUT /v3/subscriptions/{subscriptionId}: As an admin, you can update existing subscriptions using thePUT /v3/subscriptions/{subscriptionId}API endpoint by specifying input parameters.POST /v3/subscriptions: To create a new subscription, use thePOST /v3/subscriptionsendpoint. As an admin, you can create a new subscription with the following details: Subscription Name, Shared Schedules Enabled (true or false), and Default Workflow Credential ID. Once this API is executed, a subscription is created.
For more information about these endpoints, go to Subscription Endpoints.
Workflow Endpoints Updates
In order for users to maintain provenance of workflow changes, we now return sourceAppId in the response body of the following API calls:
GET/v3/workflowsGET/v3/workflow/{workflowID}GET /admin/v1/workflows/migratable
Furthermore, non-Curators can successfully make the GET v3/workflows/{workflowId} call for workflows they have access to. Previously, this was limited to Curators only. For more information, go to Workflow Endpoints.
New API Endpoint to Update Schedules
We created a new API endpoint PATCH /v3/schedules/{scheduleId} to make it possible to update a schedule without having to populate several required fields to make a single change. For more information, go to Schedules Endpoints.
New Admin Setting: Restriction to Make Workflows Public
We added the Restrict Public Workflow (Global) setting under Admin > Settings > Security. Admins can now control the way workflows are getting published - either publicly or non-publicly. To control workflows availability to other users, select or clear the Restrict Public Workflow (Global) checkbox. For more information, go to Alteryx Server Settings.
Bulk Delete for Workflows, Workflow Results, Schedules, and Collections
We added the Bulk Delete functionality for Workflows, Workflow Results, Schedules, and Collections. This allows you to delete records at once. This functionality is added to the following pages:
Workflows and Workflow Results
Admin homepage > Workflows > available for all three tabs: Private, Public, and All
User homepage > My Workspace > available for My Files (not available for Shared With Me and Public)
Schedules
Admin homepage > Schedules > available for Schedules and Designer Migrations
User homepage > Schedules
Collections
User homepage > Collections
You are now able to multi-select a workflow, workflow results, schedules, or collections using the checkbox present in each row and delete them from the page.
Before you delete the records, an alert pop-up will appear for final confirmation. Once selected records have been deleted, a snack bar message displays confirming that the selected records have been successfully deleted.
Please note that users are only able to delete workflows and schedules to which they have ownership rights. Admins can delete any workflow and any schedule. If you select multiple records, the 3-dot icon present on all records will not be displayed.
For more information, go to Delete a Workflow, Delete a Workflow via Admin Interface, Delete, Disable, or Re-Enable a Schedule, Edit or Delete a Schedule, or Delete a Collection.
New Configuration Setting: One User per Studio
For admins, we added the option to turn off shared studios by limiting the users in a studio to one. As an admin, you can now easily transfer asset ownership by transferring the workflow from one studio to another. You can then track the workflow sharing through credentials.
To limit the number of members in a studio to one user, go to Admin > Settings > Configuration > Users. Then select the Limit Studio to 1 User checkbox. For more information, go to Alteryx Server Settings.
Toggle to Show Read and Unread Notifications
We’ added a new functionality to Notifications in the upper right corner of Server UI. If you want to show only unread notifications, select the Only show unread toggle. For more information, go to Notifications.
“AMP” Column Name Renamed to “Engine”
We updated the AMP column present on various pages (such as Workflows, Schedules, and Workflow Results) to “Engine“. This column now displays the name of the engine: AMP or E1. In the previous versions, this column depicts whether a workflow is AMP enabled or not.
Loader/Spinner on Output Window While Running Analytical App
We’ve added a loader/spinner icon to the output window while running an analytical app. This depicts that job is in progress and running.
Open SSL Upgrade
We have updated the embedded OpenSSL module to version 3.0.13. This addresses the following potential vulnerabilities present in OpenSSL 3.0.12, the version shipped in 2024.1:
CVE-2024-0727
CVE-2023-6237
CVE-2023-5678
These CVEs do not affect the status of the Alteryx OpenSSL FIPS 140-2 Provider. For more information, go to Vulnerabilities 3.0.
Fixed and Known Issues
Fixed Issues
Fixed Major Release Version 2024.2.1.14 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-931 GCSE-1896 | After upgrade to 2023.1+, users can’t see their workflows in their Workspace. They can see workflows shared with them and newly published workflows only. | 2024.2.1.14 | Fixed |
TCPE-977 GCSE-1958 | Schedules > Filter by Owner doesn't load for Artisans. | 2024.2.1.14 | Fixed |
TCPE-1018 GCSE-2010 | The error “The application could not be found” occurs in Server UI after changing Run As credentials in Active Directory on now disabled Worker on Controller node. | 2024.3.1.14 | Fixed |
TCPE-1043 GCSE-1974 | Users with Chinese characters in their Alteryx Server UI logon name are not able to publish workflows to their Server. | 2024.2.1.14 | Fixed |
TCPE-1072 GCSE-2084 | Curator has access to workflows uploaded by other users via URL and workflow ID. | 2024.2.1.14 | Fixed |
TCPE-1094 GCSE-2172 | A 10060 timeout error occurs when apps attempt to access workstation files. | 2024.2.1.14 | Fixed |
TCPE-1111 GCSE-2229 | After upgrading Server from 2021.4.2.47802 to 2022.1.1.42691, and then to 2023.2.1.133, the following error appears "Error running Event #1: Func 'curl_easy_perform' failed, ret = 8, desc = Weird server reply" on workflows with email event. | 2024.2.1.14 | Fixed |
TCPE-1148 GCSE-2300 | QueueWorkerEnabled tag isn't being removed when disabling and enabling worker in Alteryx System Settings. | 2024.2.1.14 | Fixed |
TCPE-1199 GCSE-2403 | Server API requests to download workflows create YXZP files in Server UI Workspace directory which are not consistently cleaned up. | 2024.2.1.14 | Fixed |
TCPE-1244 TGAL-11745 | When running a workflow containing a Map Interface Tool on Server, the base maps do not load. | 2024.2.1.14 | Fixed |
TCPE-1250 GCSE-2554 | Desktop Automation results output engine log show incorrect time. | 2024.2.1.14 | Fixed |
TGAL-8314 GCSE-1374 | A workflow manually run from Server UI that requires user credentials is running as the local user, rather than the user credentials that were entered when 'Make these my default credentials.' is selected. | 2024.2.1.14 | Fixed |
TGAL-8401 GCSE-1474 | Update Input Data tool when Action type is “Update Input Data Tool (Default)” fails in Server UI when using the POST /users/v2/Workflows/{appid}/jobs endpoint. | 2024.2.1.14 | Fixed |
TGAL-8841 GCSE-1622 | Excel file output appears to be corrupt when retrieved from Server API call GET /v1/jobs/{id}/output/{outputId}. | 2024.2.1.14 | Fixed |
TGAL-9626 GCSE-1931 | Unable to upload workflow using V3 API when CredentialID contains Custom Groups. | 2024.2.1.14 | Fixed |
TGAL-10571 | Error message when transferring asset to member that doesn't have the correct role needs to be updated. | 2024.2.1.14 | Fixed |
TGAL-10727 | Individual select box is getting blank/unchecked after transferring multiple workflows/schedules together. | 2024.2.1.14 | Fixed |
TGAL-10747 | Clearing "Run As" credentials allows the workflow to run as default user even when the setting has been set to Require Credentials. | 2024.2.1.14 | Fixed |
TGAL-10748 | Incorrect permission error is displayed to the new owner after transferring workflow or schedule, even if they have the permission to access the workflow or schedule. | 2024.2.1.14 | Fixed |
TGAL-10749 | When transferring ownership of a workflow but no schedules to another user, the resulting snackbar on the bottom left side of the page says “Transferred workflow and schedules,” when it should say “Transferred workflow.” | 2024.2.1.14 | Fixed |
TGAL-10754 | Unable to reset the Theme settings back to default in Server. | 2024.2.1.14 | Fixed |
TGAL-10792 GBETA-452 | When transferring schedule ownership to another user, an incorrect error message is displayed and remains on the screen even though it should no longer be visible. | 2024.2.1.14 | Fixed |
TGAL-10793 GBETA-453 | When a user installs the Server API tool in Designer and creates a workflow calling GET /v3/workflows, they see the following error in their UI: Alteryx.Server.Models.Engine.AppValidation+AppValidationMessage. | 2024.2.1.14 | Fixed |
TGAL-10805 | When a user installs the Server API tool in Designer and creates a workflow calling GET /v3/workflows, no further validation message is displayed within the window. | 2024.2.1.14 | Fixed |
TGAL-10820 | The following AlteryxGallery tables appear in the AlteryxService database: credentials, dCMEConnections, dCMEShareableConnectionPortions, medias, pages, userGroups, users | 2024.2.1.14 | Fixed |
TGAL-10822 | When bulk transferring ownership of workflows or schedules, the resulting snackbar should accurately reflect what was actually transferred regardless of the radio button that was selected. | 2024.2.1.14 | Fixed |
TGAL-10846 | The POST API request to the /admin/v1/workflows endpoint in order to upload workflow returns an error message in the FIPS version of Server. | 2024.2.1.14 | Fixed |
TGAL-11044 | If multiple workflows are selected, transferred, and then a different workflow is selected, the “X workflows selected” display on the top right is not refreshing to the correct number of selections. | 2024.2.1.14 | Fixed |
TGAL-11089 GCSE-2250 | AlteryxService fails to start up when configuring Alteryx Designer for Designer and Scheduler Only. | 2024.2.1.14 | Fixed |
TGAL-11105 GCSE-1859 | The versionNumber field returns all zeros from the API for workflows uploaded in the previous Server version. | 2024.2.1.14 | Fixed |
TGAL-11124 GCSE-1906 | The File Browse Tool is unable to upload an XLSX file, returning the error: "No table chosen; Please select a Table from data source. (ToolId: 4)" | 2024.2.1.14 | Fixed |
TGAL-11159 GCSE-2197 | The Server UI displays the incorrect time for Asia-Almaty, showing +6 when it should be +5. | 2024.2.1.14 | Fixed |
TGAL-11249 GCSE-2339 | The reindex command line does not generate logging. | 2024.2.1.14 | Fixed |
TGAL-11256 GS-4957 | The GET /v3/jobs/{jobId} endpoint doesn't allow users to see job results via collection. | 2024.2.1.14 | Fixed |
TGAL-11268 GCSE-2338 | The CryptoMigration log (AlteryxServiceMigrator_#.log) incorrectly categorizes the new error as state ;4; instead of ;3;. | 2024.2.1.14 | Fixed |
TGAL-11272 TPRI-1122 | New Server UI: In both user and admin Schedules, the schedule status filter does not work. When users select or clear any of the checkbox options in the filter for the Status column, an empty page with the "No Schedules." message is displayed. | 2024.2.1.14 | Fixed |
TGAL-11282 GCSE-2344 | Crypto Migration Summary counts for PackageDefinitions and AppChunks do not match as expected. | 2024.2.1.14 | Fixed |
TGAL-11287 | The alteryx.config file previously allowed overriding the default executionPriority (QoS) for certain types of job executions, but this functionality no longer works. | 2024.2.1.14 | Fixed |
TGAL-11347 | When a user who used to have V3 API access in Server is changed to ‘No Access’ role, they are still able to successfully make requests against the API. | 2024.2.1.14 | Fixed |
TGAL-11347 | When a user who used to have v3 API access in Server is changed to ‘No Access’ role, they are still able to successfully make requests against the API. | 2024.2.1.14 | Fixed |
TGAL-11407 | When you run the seeded SqlServer DB and navigate to Credentials, an exception is thrown. The Credentials table is shown with a single row that says “ERR”. | 2024.2.1.14 | Fixed |
TGAL-11440 GCSE-2431 | SQL Server DB schedules do not run the published version of the workflow, but the version from when the schedule was created. | 2024.2.1.14 | Fixed |
TGAL-11458 GCSE-2430 | Schema Migration 49 is failing on upgrades to 2024.1 if various Messages, DatasetMessages, or TagIds arrays in appInfos records are missing or contain null values. | 2024.2.1.14 | Fixed |
TGAL-11459 GCSE-2442 | When upgrading from 2021.4 to 2024.1, Gallery schema migration will fail and prevent Server from loading post upgrade. | 2024.2.1.14 | Fixed |
TGAL-11460 GCSE-2437 | When migrating to 2024.1, Server will fail to migrate with the Migration 49 error when the Filename field in the PrimaryApplication object within a revision is invalid or contains an empty name. | 2024.2.1.14 | Fixed |
TGAL-11502 | A 500 response code is returned when making a GET call with a datetime parameter while using SQL as the database. | 2024.2.1.14 | Fixed |
TGAL-11761 | Unable to add a user group to credentials via the public API or UI when using SQL as the database. | 2024.2.1.14 | Fixed |
TGAL-11800 GCSE-2597 | The existence of the MongoDB index CreationDateTime_-1 in the AS_Queue collection is causing Service Migration 2 to fail without providing a useful error message. | 2024.2.1.14 | Fixed |
TGAL-11901 GCSE-2587 | Analytic app error – ParseError: Expected entity name for reference at line 1, column XXX while processing "WizardValues" (ToolId: -1). | 2024.2.1.14 | Fixed |
TPRI-1453 GCSE-537 | A blank screen appears when attempting to edit a schedule that was disabled because the associated application was deleted. | 2024.2.1.14 | Fixed |
TPRI-1603 GCSE-1328 | The "Name" and "Workflow" columns should display a message indicating that the workflow linked to the schedule has been deleted. | 2024.2.1.14 | Fixed |
TPRI-4718 GCSE-1915 | Clearing the current system message generates a new empty notification for users instead of simply dismissing the previous one. | 2024.2.1.14 | Fixed |
TPRI-5380 GCSE-2151 | Analytic app > Interface Designer > On Success > No Output Files Message doesn't appear when run on Server. | 2024.2.1.14 | Fixed |
TPRI-5409 GCSE-2154 | Radio buttons and Labels are out of order in Server UI. | 2024.2.1.14 | Fixed |
TPRI-5461 GCSE-1704 | Windows Auth: Email column field displays Windows Identity Name and not the Email address. The column field header should be Windows Identity. | 2024.2.1.14 | Fixed |
TPRI-5570 GCSE-2192 | Unable to select multiple checkboxes when the values in the List Box tool in the Analytic App are identical. | 2024.2.1.14 | Fixed |
TPRI-5661 GCSE-2007 | The third chained app fails to load the output file generated by the first app when running on Server. | 2024.2.1.14 | Fixed |
TPRI-5694 GCSE-2198 | The dropdown tool behaves incorrectly when a default response is used for field mapping. | 2024.2.1.14 | Fixed |
TPRI-5773 GCSE-1534 | Last App in series of at least 3 chained Apps fails to read the output file from the first App. | 2024.2.1.14 | Fixed |
TPRI-5918 GCSE-1508 | Theme colors apply to curators only. | 2024.2.1.14 | Fixed |
TPRI-5954 GCSE-2346 | Tree tool in a chained app does not work. | 2024.2.1.14 | Fixed |
TPRI-6408 GCSE-2526 | Schedule does not work for Analytic Apps. | 2024.2.1.14 | Fixed |
TPRI-6498 GCSE-2584 | The Job Results page becomes unresponsive and fails to load log messages when the log size is excessively large. This can eventually result in either a RESULT_CODE_HUNG or an "Out of Memory" error. | 2024.2.1.14 | Fixed |
Fixed Minor Release Version 2024.2.1.41 | |||
|---|---|---|---|
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. | 2024.2.1.41 | Fixed |
TCPE-1265 GCSE-2579 | The SharePoint tool (version 2.1.0) running on Server 2.1.0 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. | 2024.2.1.41 | 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. | 2024.2.1.41 | Fixed |
TGAL-11942 | A subscription user is unable to view the analytic app wizard values of the subscription owners schedule on the GET /v3/schedules/{scheduleId} endpoint. | 2024.2.1.41 | Fixed |
TGAL-11943 | A subscription user is unable to update analytic app wizard values on the following schedule endpoints: PUT /v3/schedules/{scheduleId} and PATCH /v3/schedules/{scheduleId}. | 2024.2.1.41 | Fixed |
TGAL-11965 | When using the GET /admin/v1/subscriptions endpoint, a 500 Internal Server Error appears. | 2024.2.1.41 | Fixed |
TGAL-11968 | When syncing Azure AD Groups by SCIM, a 500 Internal Server Error occurs. | 2024.2.1.41 | Fixed |
TGAL-11983 | When using the GET /admin/v1/users endpoint, a 500 Internal Server Error appears. | 2024.2.1.41 | Fixed |
TGAL-11985 | Users with access to a schedule through a collection should not have the ability to delete the schedule. | 2024.2.1.41 | Fixed |
TGAL-11993 | The DELETE/v3/schedules/{scheduleId} request is returning a 500 Internal Server Error response for SQL DB. | 2024.2.1.41 | Fixed |
TGAL-12062 | Deleting the analytic app used to create a schedule results in error when loading the Schedule UI. | 2024.2.1.41 | 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. | 2024.2.1.41 | Fixed |
Known Issues
Known Major Release Version 2024.2.1.14 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-1308 GCSE-2733 | The Server environment is generating a large volume of error logs in C:\Programdata\Alteryx\Errorlogs\AlteryxE2. All error log files contain the same error: "Issue: Invalid parameter detected in function (null). File: (null) Line: 0 Expression: (null)." | 2024.2.1.14 | Known |
TGAL-11943 | A subscription user is unable to update analytic app wizard values on the following schedule endpoints: PUT /v3/schedules/{scheduleId} and PATCH /v3/schedules/{scheduleId}. | 2024.2.1.14 | Known |
TGAL-11961 | When using the PATCH /v3/schedules/{scheduleId} endpoint to update the iteration to a future time on the same day, a 400 error appears with the message: "Start date must be in the future." | 2024.2.1.14 | Known |
TGAL-11985 | Users with access to a schedule through a collection should not have the ability to delete the schedule. | 2024.2.1.14 | Known |
TGAL-11993 | The DELETE/v3/schedules/{scheduleId} request is returning a 500 Internal Server Error response for SQL DB. | 2024.2.1.14 | Known |
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. | 2024.2.1.14 | Known |