This topic lists any bugs that have been fixed between versions 2025.1.1 and 2025.2 of InfoWorks ICM.
See Known Limitation and Issues for a list of limitations and any issues that we are aware of.
The fixes listed below 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.
Subcatchment flow to node result
Since version 2023.2, a subcatchment with "Groundwater infiltration node" explicitly set to the same node as the drains to "Node ID" had groundwater flow double-counted in the flow to node result. This bug did not arise when the "Groundwater infiltration node" is blank, in which case the groundwater flow also goes to the drains to "Node ID" node but was not double-counted. The issue has now been fixed, and the online help has been updated to explain the behaviour more clearly.
Remote simulations on Autodesk-branded installations
Since release 2025.0, simulations would only run remotely on a remote agent with an Innovyze-branded InfoWorks ICM installed. From 2025.2 onwards, both Innovyze- and Autodesk-branded installations can act as a remote agent using a Thales licence. If both are installed, then the installation of the same brand as the instance of InfoWorks ICM from which the simulation was scheduled is used to run the simulation.
Remote simulations on agent-only installs
In 2025.0 and 2025.1, an error in the installer meant that simulations sent to a remote machine with only the Innovyze Remote Agent installed failed with an error in the log "FAILED" following the "Starting SimPostP engine" message at the end of the simulation. This could be worked around either by installing the full Innovyze version of InfoWorks ICM or by copying SwmmNetDB.dll from a full installation into the Remote Agent installation. The installer has now been repaired and the Remote Agent is functioning again.
Subcatchment property editor
The subcatchment property editor should now update automatically when related land uses are changed.
Importing from InfoSWMM
A crash when importing an InfoSWMM model containing long time series data into a model group has been fixed.
Copying global preferences when there are none
There should no longer be an "Error 51" dialog when trying to paste global preferences from another database that contains no global preferences into a cloud database.
Emptying the recycle bin
An "Error 12: No Such Record" message when trying to empty recycle bin in some circumstances has been fixed, and it should now be possible to empty the bin.
Importing rainfall from InfoSWMM
When importing an InfoSWMM model, rainfall volumes and depths should now be converted correctly to intensity.
Storage compensation
Storage compensation is now calculated correctly when a subcatchment drains to multiple links.
Using cloud databases with usernames containing non-Latin characters
It is now possible to use a cloud database when logged in to Windows with a username containing non-Latin characters, although it is still necessary to specify a results route whose path contains only Latin characters.
SWMM simulations with backslash characters in node names
The fix for simulations failing in the cloud when using a network containing a node with a "\" character in its name has now been extended to SWMM networks.
Theme colours and auto-range
Toggling "restrict auto range" no longer changes theme colours.
Subcatchment validation
Validation now only requires drying time to be specified for subcatchments using CNSWMM runoff volumes.
Intelligent network search
When "intelligent network search" is selected, clicking on a node, link, point or line on the GeoPlan when there is a polygon object (e.g. a subcatchment) behind it now selects the non-polygon object without further confirmation.
Custom graphs
Some crashes in custom graph generation have been fixed.
Importing climatology from InfoSWMM
The "evaporate only during dry periods" option is now imported correctly from InfoSWMM.
Commit history numbering
In cloud databases, the first item in the commit history of a network that has been copied from another network is now numbered 1, as has always been the case in workgroup and standalone databases.
Unexpected side-effects of renaming a node
In some circumstances, renaming a node could cause unwanted changes to other properties with the default (#D) flag set. This has been corrected.
Table not found error when opening a branched network
When a new branched network is created in a Workgroup or Standalone database from an existing branch copied from a cloud database, attempts to open the new branch sometimes failed with a "Table not found" error. This has been fixed.
Water quality simulations
Some intermittent failures in water quality simulations run in on-premise databases have been fixed.
Scalar TSD grid
Shortcut keys Ctrl+X, Ctrl+C and Ctrl+V now work for cut, copy and paste in the scalar TSD grid view.
Importing rainfall timeseries from InfoSWMM
Rainfall timeseries in external files should now be imported correctly from InfoSWMM. Previously there was an issue with computing the time interval.
Time series import from XPSWMM
The import of fixed interval time series data from XPSWMM now sets a suitable fixed time increment, and no longer generates unnecessary subevents.
Font scaling in print layout
In print layout views, font scaling is now applied to link end labels on GeoPlans.
Permeable zone instantaneous infiltration result
The instantaneous infiltration result on permeable zones is now explained more clearly in the help. The result itself has not been changed.
Unexplained crashes
Various unexplained crashes in the software have been fixed.
Object not found in network error when opening results
An "Object not found in network" error when opening results for networks containing conduits of type "culvert" has been fixed. This was a regression introduced in version 2025.0.
Clip meshing missing some bank connections between rivers and 2D zones
Following a regression introduced in release 2023.2, clip meshing was missing some parts of river banks that are not colinear with the 2D zone boundary and failing to make a connection between the river and the 2D zone. This has ben fixed.
Spatial rain sources
Spatial rain source objects with source type set to "Spatial TSDB Observed" or "Spatial TSDB Forecast" were not being correctly recognised by the software following the nomenclature change from TSDB to TSD. These source types have been reinstated to fix this.
Proxy server for cloud access
There have been difficulties, on occasion, with access to cloud databases if a proxy server is used. This has been addressed.
See Cloud Connection Requirements for measures you should take.
Vulnerabilities
The following vulnerabilities have been fixed:
CVE-2022-25942, CVE-2022-25972, CVE-2022-26061, CVE-2018-25032, CVE-2021-46822, CVE-2020-35538, CVE-2020-13790, CVE-2018-14550, CVE-2018-19664, CVE-2018-13785, CVE-2018-1152, CVE-2023-45853, CVE-2022-37434, CVE-2020-17541, CVE-2019-2201, CVE-2019-7317, CVE-2018-14498, CVE-2018-20330
See the Autodesk Trust Center for details about vulnerabilities in InfoWorks software.