I've encountered a bug in Zenon Logic where the timestamp of an internal variable (Driver for internal variables) is not updated when the variable's value is changed from within Zenon Logic.

This leads to several issues:

• Alarm message list displays incorrect timestamps for when the alarm occurred.

• The alarm duration is shown as 0 seconds once the alarm is cleared.

• An archive configured with "on change" mode is likely storing the value with an incorrect timestamp, resulting in misleading trend displays.

The project settings are correctly configured to enable timestamps for the internal driver. A screenshot of the settings is attached. Additionally, I have recorded a short video demonstrating the issue.