Values within a EPO 2022 project are misbehaving during project runtime

Issue
Values within a EPO 2022 project have been misbehaving when attempting to start a project runtime within a production environment. The values seem to be getting corrupted/changed when services stand up during a recompile. The values being changed effect DBFs:
System Model > Alarms > Analog Alarms
System Model > Alarms > Advanced Alarms

It was also noted that the 'High' alarm threshold values were automatically changing from 1 to 3.40e+38, and alarm delays were reverting to 0 (00:00:00), causing nuisance alarm flooding and preventing breaker state change events from being captured.

Resolution

• We identified the issue was caused by the [Alarm]UseConfigLimits parameter set to 1 in the Citect.ini file, which prevented proper synchronization of alarm property changes between redundant servers.
• We recommended setting [Alarm]UseConfigLimits = 0 to allow changes made offline in the project to deploy correctly with restarts on Standby and Primary servers.
• We also provided details of two related bugs: 3045403 (fixed in EPO2022 CU7 and EPO2024 CU2) and 4003810 (fixed in EPO2024 CU3, not fixed in EPO2022) affecting writable alarm properties with UseConfigLimits=1.

Released for: Schneider Electric Australia