Upgrades using the silent installer no longer fail because validation runs.

An ArgumentOutOfRangeException in the Job Engine no longer prevents IPAM from discovering subnets.

Opening Performance Analysis Dashboard (PerfStack) projects no longer causes performance problems such as high CPU usage on the server and slow page loading in the SolarWinds Web Console.

Variables included in alert definitions consistently return the correct results.

The Configuration Wizard no longer fails during an upgrade if it cannot write information about migrated credentials into the database. The issue is logged as a warning, and the configuration continues.

Clicking the link for more information in a license notification no longer returns a 404 error.

An issue with the database has been fixed, and Meraki response time polling is no longer slow.

If ServiceNow has Authentication profile configuration, requests no longer fail with the message User Not Authenticated.

A problem with the Cisco Buffer Failures widgets that caused performance problems in the SolarWinds Web Console is fixed.

If the AllowSwaAutoUpdate centralized setting is set to false, the SolarWinds Administration Service is not automatically updated if the user opens the Updates page.

When you update an advanced configuration setting, a message on the Advanced Configuration page tells you if any services need to be restarted for the change to take effect and provides an option to restart those services.

Container synchronization has been improved to prevent an issue that triggered HA failovers in environments with high latency between additional polling engines and the database.

The performance of the UnManageUtility tool in large environments is improved.

If there is a delay in an alert action, the alert no longer retries the action, appearing to perform the same action multiple times.

A delay in one alert does not prevent other alerts from being triggered, cause a deadlock that stops alert processing, or block alert notifications for other alerts.

When a node with some traffic statistics is down, maps do not show connections as green, which would indicate that the node is up.

Intelligent Maps can be filtered using a custom property whose name includes special characters.

Multiple stored procedures were optimized to prevent deadlocks in the SolarWinds Platform database.

When a user's Windows or SAML group membership changes, information about the user's group limitations is updated in the SolarWinds Platform, and widgets display the correct data for that user.

The performance of the Administration Service has been improved to prevent it from consuming large amounts of CPU and other resources.

When you remove and then re-add a WSUS server from Patch Manager, that server is no longer listed multiple times in widgets on the SolarWinds Platform Patch Manager Summary page.

If an action is intentionally not executed when an alert is triggered (for example, because the action is disabled or paused), restarting the alerting service does not cause the action to be executed.

The SolarWinds Platform database no longer includes non-trusted foreign keys.

If index defragmentation fails, it no longer prevents database maintenance from completing.

The Database Details page is displayed correctly on Azure SQL.

The OrionWeb.log file is no longer filled with warnings about a failure to open the registry key.

Users with the Allow map management privilege but without the Allow nodes management privilege can create maps.

When there are multiple polling engines and a disabled plug-in needs to be uninstalled, the correct agent management service uninstalls the plug-in.

If you open multiple user accounts in multiple tabs and edit one account, changes are applied to the correct account.

When you include a PerfStack chart in a report that is distributed as a PDF, the bottom of the chart is no longer cut off.

On the Node Details page, the time required to load the All Dependencies widget and all widgets associated with alerts has decreased, improving the performance of the SolarWinds Web Console.

In a large deployment, when you group nodes on the Manage Nodes page by a custom property, the page loads much faster.

PerfStack projects display data correctly after an upgrade. In early 2024.1 RC builds, the start and end times configured for the widgets were reset to have the same value, and therefore no data was displayed.

After the main polling engine is upgraded, centralized upgrades now continue upgrading scalability engines (additional polling engines, additional web servers, and high availability servers) as expected. In early 2024.1 RC builds, centralized upgrades stopped without upgrading scalability engines.

If an alert listed on the All Active Alerts page contains a custom property with a non-string value (for example, a date or Boolean value), searching that page no longer returns an error.

Group objects expand correctly when a search string contains RegEx.

Database maintenance removes all temporary system files.

When a Windows agent loses connection with the SolarWinds platform for a long period, it resumes sending data when the connection is reestablished, and data collected while the agent was disconnected is synchronized to the SolarWinds Platform database.

JobEngine performance has been improved to prevent an issue that resulted in jobs being canceled or removed from agents.

**Seed Router discovery now supports the most recent RFC standards used by device types like Cisco Catalyst 4500, Cisco CGR-2010, Cisco 4451X, and Arista devices. When a network includes newer devices like these, using Seed Router discovery no longer fails with the following error:

Unable to find subnets

**Unresponsive or slow agents in an environment with many agents no longer cause an issue with the JobEngine service. This issue could result in missed or delayed polling and agent nodes with a status of Unknown.

Old .APKG files (Agent plugin packages) are now removed when SolarWinds Platform agents are upgraded.

When DPAIM users with an SRM license attempt to create a relationship between a database and a storage object, they no longer see a message that SRM is not installed, and the relationship can be created.