Below, you will find a categorized list of known limitations and issues in
InfoWorks WS Pro 2024. While this list is not comprehensive, it should serve as a useful reference of important issues to guide you as you upgrade your software and database versions.
Note: This list does not include any issues resolved prior to or included in the 2024.0 release. To understand the status of older versions, please refer to
2024.0 and
earlier release notes.
| General
|
Reported In
|
Status
|
*DB Update Required
|
|---|
| There is an issue with the efficiency of Hydrant Test Fire Flow GMR. See
Cloud Multi-run Workflow for advice when running Fire Flow Hydrant tests as multi runs.
|
2024.5
|
Open
|
|
| When importing from a CSV file into a GMR Configuration with ISO8601 dates, a crash could occur.
|
2024.2
|
Resolved in 2024.4
|
No
|
| Global UPC named actions not working as expected.
|
2024.1
|
Resolved in 2024.4
|
No
|
| Objects are not being deleted and removed from Workgroup Server database folder when deleted in the software.
|
2024.0
|
Resolved in 2024.4
|
No
|
| In the
User Defined Field Names dialog, if you open a database for version 2024.3 or earlier, then some tables appear twice in the Table drop-down list.
|
2024.3
|
Resolved in 2024.4
|
No
|
| SELECT clauses do not work properly with scenarios in SQL queries.
|
2024.1
|
Resolved in 2024.3
|
No
|
| When merging from another network, a crash occurs and the network is not deleted after the merge.
|
2024.0
|
Resolved in 2024.3
|
No
|
| Labels are not exported to AutoCAD DWG.
|
2023.2
|
Resolved in 2024.3
|
No
|
| GMR summary report settings are sometimes not saved correctly.
|
2023.2
|
Resolved in 2024.3
|
Yes
|
| Simulation and Analysis
|
Reported In
|
Status
|
*DB Update Required
|
|---|
| Fire Flow hydrant testing runs produce false error messages that prevented analysis if the start and end times do not align with the Control start and end times.
|
2024.1
|
Resolved in 2024.3
|
Yes
|
| Fire Flow simulations are switching back to the Base scenario when the run begins.
|
2024.1
|
Resolved in 2024.3
|
Yes
|
| Changing a run type between a type that does not support scenarios and a type that supports scenarios leads to a conflicting message in the scenario choice list.
|
2023.2
|
Resolved in 2024.3
|
Yes
|
| Cloud Databases
|
Reported In
|
Status
|
*DB Update Required
|
|---|
| If a database is restored from the database management web portal but its original copy is deleted, version controlled objects like networks will be unable to open.
|
2024.0
|
Open
|
|
| User permissions cannot be applied to cloud databases. Any member in a team will have access to the team's hub.
|
2024.0
|
Open
|
|
| Trying to theme customer points pressure would result in a crash as the customer points pressures were not being generated on the cloud.
|
2024.2
|
Resolved in 2024.4
|
No
|
| An "error getting blobs" message arises when copying networks from cloud databases. This occurs for networks containing large numbers of changes to large network objects in multiple commits.
|
2024.1
|
Resolved in 2024.3
|
Yes
|
| Copying to a Cloud database from Oracle or SQL-Server Workgroup database.
|
2024.5
|
Resolved in 2025.0
|
No
|
| Cloud Simulations
|
Reported In
|
Status
|
*DB Update Required
|
|---|
| Cloud databases currently have a soft limit of 80 concurrent simulations.
|
2024.0
|
Open
|
|
| Cloud simulations will download results to the local machine when selected. InfoWorks WS Pro currently does not monitor local storage capacity for the results, and the software may freeze if it runs out of storage.
|
2024.0
|
Open
|
|
|
If the user wishes to use a base run to provide nominal pressure, so that demand efficiency can be calculated, then a cloud Pressure Related Demand run will not provide demand efficiency results. The workaround is to update nominal pressures in the network (from network menu) and then do a pressure related run in the cloud without a base run.
|
2024.5
|
Open
|
|
| Cloud simulations appear to have failed in both the Job Control window and the Explorer tree if a user logs out of Windows or WS Pro. 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.0
|
Resolved in 2024.5
|
|
*DB Update Required
- Issues in rows with a "Yes" in this column require 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.
