This document lists product fixes which have been made in InfoWorks WS Pro 2026.3.
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.
Cloud and on-premise runs for Fire Flow Hydrant Test, Forced Fire Flow and GMR now support single scenarios.
Selecting the top (empty) row from the Field type selection list for a SQL spatial search could cause the application to crash. This has now been addressed.
Importing point based valves from File Geodatabases was not working correctly. This has now been addressed.
When re-running a "run", the run did not correctly pick up the change to use the base scenario after having been run with a non-base scenario. This has now been fixed.
When configuring fixed speed / variable speed pumps, the status of the initial speed column in non-base scenarios was incorrectly linked to the status of the base scenario configuration. This has now been corrected, each scenario is now independent.
The "spatial_data" field on pipes did not work for SQL and Ruby. This is fixed.
After deleting a demand diagram associated with a network, sometimes the associate control dialog could not be opened. This is fixed.
Switching between categories in a Demand Diagram with a live data configuration in the background was very slow. This is fixed.
Customer point results were incorrect for transient runs. This is fixed.
When an object is open for edit in a cloud database, and the database is moved to a different project - the UI could crash when trying to save the object. This has now been addressed.
Opening the fields and verification tabs on the Baseline was very slow for large networks. This is fixed.
Non-base scenario runs for Fire Flow Hydrant tests could be susceptible to having limited results shown. This has now been addressed.
Deleting a scenario using the "Delete scenario" button often did not work. This is fixed.
The open channel shape value being passed from the pre-processor to be used by the engine could be incorrect in some instances. This has now been addressed.
There was an issue where hidden model groups could slow down the opening of the explorer tree. This is fixed.