The known limitations and issues in the 2024 versions of InfoWorks ICM are listed in the following sections.
Known Limitations
Version 2024.0 was the first release of InfoWorks ICM with buildings and cloud capabilities. The following limitations apply to this new functionality:
| Cloud databases | Release Version | Limitation Lifted Version | *DB Update Required |
|---|---|---|---|
| Results cannot currently be copied from a cloud database to an on-premise database either directly or via a transportable database. | 2024.1 | 2024.3 | No |
| Objects with a commit history cannot currently be copied from a cloud database to an on-premise database either directly or via a transportable database. Users will need to export this data to CSV or Snapshot files if they wish to copy the data. | 2024.0 | 2024.1 | No |
| User permissions cannot be applied to cloud databases. Any member in a team will have access to the team's hub. | 2024.0 | ||
| Risk objects cannot be copied or created in a cloud database. | 2024.0 | ||
| TSDB objects cannot be copied or created in a cloud database. | 2024.0 | 2025.0 | No |
| Ground models greater than 2GB cannot be uploaded. | 2024.0 | 2025.0 | No |
| InfoAsset Manager objects cannot be copied, created or used as background networks when working in a cloud database. | 2024.0 | ||
| Result objects cannot be copied to a cloud database. These simulations must be re-run. | 2024.0 | ||
| Result objects copied from another cloud database or transportable incorrectly indicate that results are available. | 2024.0 | 2024.3 | No |
| Cloud databases do not allow re-runs. | 2024.0 | ||
| Creating a copy of a network from the version history can sometimes create a corrupted network which cannot be opened. | 2024.0 | 2024.3 | No |
| If a cloud database is restored from the Info360 Model Management web portal but its original copy is deleted, version controlled objects, such as networks, will be unable to open. | 2024.0 | 2024.3 | No |
| Database groups are not currently available for cloud databases. | 2024.0 |
| Cloud simulations | Release Version | Limitation Lifted Version | *DB Update Required |
|---|---|---|---|
| ICMExchange - Cloud simulations cannot be launched from ICMExchange | 2024.2 | 2024.4 | No |
| Cloud simulations appear to have failed in both the Job Control window and the Explorer tree if a user logs out of Windows or ICM. The simulation continues but is not visible in the Job Control window. The user can delete the local failed result and once the simulation is complete the results will be available. | 2024.1 | 2024.4 | No |
| Cloud databases have a soft limit of 80 concurrent simulations. | 2024.0 | ||
| Cloud simulations simulating with GPU compute have a memory limit of 16GB (~20M elements). Larger simulations must be run on CPU. | 2024.0 | ||
| Risk runs cannot be simulated in the cloud. | 2024.0 | ||
| Runs with TSDB inputs cannot be simulated in the cloud. | 2024.0 | 2025.0 | No |
| Simulations which exceed the monthly quota cannot be run in parallel. It is not currently possible to increase or share monthly quotas. | 2024.0 |
| Differences in engine results | Release Version | Limitation Lifted Version | *DB Update Required |
|---|---|---|---|
|
Cloud and on-premise simulations may give varying results in numerically sensitive models where the solution is on the edge of a mode (for example pumps on or off), oscillates between modes or has difficulty converging. Although the engine solvers are identical, they are compiled using different mathematical optimisations. Neither result is more accurate than the other. This behaviour can also occur when running on-premise simulations on different hardware configurations where calculations are distributed across multiple cores, use different processor architecture and/or use of GPU instead of CPU for 2D calculations. |
2024.3 | See Engine changes |
| Buildings | Release Version | Limitation Lifted Version | *DB Update Required |
|---|---|---|---|
| Building polygons cannot be used outside of a 2D zone. | 2024.0 | 2024.1 | No |
Known Issues
A categorised list of known issues in 2024 versions is included below. While this list is not comprehensive, it provides a useful reference of important issues to guide you as you upgrade your software and database versions.
| File Geodatabases | Release Version | Status | *DB Update Required |
|---|---|---|---|
| Exporting to a File Geodatabase using the automapping option creates data that cannot be viewed. | 2024.0 | Resolved in 2024.1 | No |
| When using File Geodatabase in the Open Data Import Centre, only files in the first level folders will be imported. | 2024.2 | Resolved in 2024.3 | No |
| When using File Geodatabase in the Open Data Export Centre, files will only be exported to first level folders. | 2024.2 | Open | No |
| Help Menu | Release Version | Status | *DB Update Required |
|---|---|---|---|
| The Check for updates option in the Help menu no longer works. | 2024.0 | Permanently removed | No |
| SWMM5 and InfoSWMM import | Release Version | Status | *DB Update Required |
|---|---|---|---|
| Importing from SWMM5 or InfoSWMM to a SWMM network creates a run that fails. Users will need to check the Update to latest box in the Run dialog to run the simulation. | 2024.0 | Resolved in 2024.2 | No |
| Backward compatibility | Release Version | Status | *DB Update Required |
|---|---|---|---|
| Results from a simulation, run in a 2024.0 and above client, cannot be opened in a 2023.x client and must be re-run. | 2024.0 | Resolved in 2024.5.3 | No |
*DB Update Required - Any row with a "Yes" in this column requires the database version to be updated to at least the version it was initially resolved in. For most engine-related issues, you will need to upgrade the software as well as the database.