This document lists product fixes which have been made in InfoWorks WS Pro 2025.5.
See Known Limitations and Issues for a list of limitations that we are aware of.
The fixes listed here are those that are viewed as likely to impact on users in an unexpected way, mainly changed simulation results, or differences in behaviour that might not be obvious.
SQL Themes were not working with scenarios. This is fixed.
Select On GeoPlan for a Control Node in a Pump Station was not working. This is fixed.
During the import from XINP, the network and control descriptions were not set. This is fixed.
The demand profile export did not take into account the daily and monthly factors. This is fixed.
Fixed head profiles were imported incorrectly from EPANET (INP). The profile was taken as the head instead of multiplying the fixed head with the profile. This is fixed.
Lagrangian WQ runs can consume so much RAM that performance is poor and machines may freeze and/or shutdown. This is fixed.
It was not possible to run a simulation and open it in the same script. This is fixed.
The time-zone field in the live data logon grid did not synchronize properly with the property editor. This is fixed.
When test cases that use hydrant curves, the output column names may incorrectly be prefixed with a comma. Consequently, the hydrant curve may not be viewable from the report grid. This is fixed.
The Results Selector can be used to reduce the volume of results. This is the default in cloud runs. If pressure, demand, status, or leakage results were missing for the service level analysis, the service level analysis would silently fail. This is fixed.
A warning is displayed so that the failure is no longer silent.
In order to work around this problem fully, change the settings of the Results Selector in the run to produce Fully Results, or to allow pressure, demand, status, and leakage to be written.
In some reports, there were differences in decimal precision between cloud and desktop runs. This is fixed.
Cloud Orchestrated Multi Runs can silently fail when run locally. This is fixed.
The Cloud engine was not correctly reporting the type of machine in use for a particular run. This is fixed.
If WS Pro and WS Pro Viewer simultaneously open the same network on the same machine, then the software will crash if an edit is attempted.
This is fixed. A warning is displayed.
The ADSK WS Pro Viewer is not intended to modify and run simulations. Nevertheless, the ADSK WS Pro Viewer could copy and paste of cloud runs. The copied runs could not be edited or run, but the capability was misleading.
This is fixed. The ADSK WS Pro Viewer cannot copy and paste cloud runs
Sometimes updating the Demand Diagram from the Demand Area Analysis did not work. This is fixed.