The following lists detail the various maintenance fixes made in InfoWater Pro version 2025.3.
For a list of the latest features and improvements in the current release, refer to What's New.
Design fireflow search range when running on domain only
Previously, when running fireflow on domain only, InfoWater Pro would restrict the critical node search range to the domain if using the default setting of Fire Nodes. This has been updated so the Fire Node search range will always include all nodes with defined fireflow. This enables easier testing of a few hydrants while considering the full network impacts. The other critical node search range options (Entire Network and Selection Nodes) are unaffected by this change.
Fire flow and pressure-dependent demand
Pressure-dependent demand was not compatible with fire flow calculations. This is now resolved by ignoring the local impacts of pressure-dependent demand at each hydrant during analysis.
Results API and new engine
The python results API did not work for outputs from InfoWater Pro 2025.2 due to engine updates. This has been resolved.
Issue with comma in file path blocking Simulation Task Manager
The Simulation Task Manager for cloud and background simulations was unable to run when the model was stored with a comma in the file path. This is now resolved.
InfoSurge range output with Selection
An error was causing incorrect reporting of Min and Max flow results for Surge range reports when using a selection set. This has been resolved.
SCADA run memory issue when run duration doesn't line up with SDA event
For some SCADA runs with irregular SCADA data timesteps, the engine would run into a memory issue and fail to complete at the end. This has been made more reliable for producing runs with varying SCADA event lengths.
Issue opening pattern table with large amount of data
An issue was preventing the DB Editor opening Pattern data with tens of thousands of rows. This has been resolved.