Timestamp wrong in Data Viewer

[huganega]

The Problem

The timestamp in the Data Viewer is always displayed incorrectly in the event of an error; the time stamp is only correct again if there is no error.

2022-12-28T16:32:41+0100,main,583.5888,583.5888,583.5888,0.000060,0.0003,no error,5.0,8.0,3.4,6.0,8.7,8.7,8.1
2022-12-28T16:37:41+0100,main,583.5930,583.5930,583.5930,0.000840,0.0042,no error,5.0,8.0,3.3,6.0,8.9,3.3,0.4
2022-12-28T16:37:41+0100,main,583.5841,,583.5930,,0.0042,Neg. Rate - Read: - Raw: 583.5841 - Pre: 583.5930 ,5.0,8.0,3.4,6.0,9.0,4.0,1.2
2022-12-28T16:37:41+0100,main,583.5841,,583.5930,,0.0042,Neg. Rate - Read: - Raw: 583.5841 - Pre: 583.5930 ,5.0,8.0,3.4,6.0,9.0,4.0,1.2
2022-12-28T16:52:41+0100,main,583.5941,583.5941,583.5941,0.000073,0.0011,no error,5.0,8.0,3.4,6.1,9.0,4.0,1.2
2022-12-28T16:57:41+0100,main,583.5945,583.5945,583.5945,0.000080,0.0004,no error,5.0,8.0,3.4,6.0,9.0,4.4,5.3
2022-12-28T17:02:41+0100,main,583.5945,583.5945,583.5945,0.000000,0.0000,no error,5.0,8.0,3.3,6.0,9.0,4.5,5.4
2022-12-28T17:07:41+0100,main,583.5967,583.5967,583.5967,0.000440,0.0022,no error,5.0,8.0,3.3,6.0,9.4,6.6,7.9 

Version

Release: v13.0.8 (Commit: 04f2f23+)

Logfile

2022-12-28T16:22:41+0100,main,583.5885,583.5885,583.5885,0.000000,0.0000,no error,5.0,8.0,3.3,6.0,8.7,8.4,5.3
2022-12-28T16:27:41+0100,main,583.5885,583.5885,583.5885,0.000000,0.0000,no error,5.0,8.0,3.4,6.0,8.7,8.4,5.3
2022-12-28T16:32:41+0100,main,583.5888,583.5888,583.5888,0.000060,0.0003,no error,5.0,8.0,3.4,6.0,8.7,8.7,8.1
2022-12-28T16:37:41+0100,main,583.5930,583.5930,583.5930,0.000840,0.0042,no error,5.0,8.0,3.3,6.0,8.9,3.3,0.4
2022-12-28T16:37:41+0100,main,583.5841,,583.5930,,0.0042,Neg. Rate - Read: - Raw: 583.5841 - Pre: 583.5930 ,5.0,8.0,3.4,6.0,9.0,4.0,1.2
2022-12-28T16:37:41+0100,main,583.5841,,583.5930,,0.0042,Neg. Rate - Read: - Raw: 583.5841 - Pre: 583.5930 ,5.0,8.0,3.4,6.0,9.0,4.0,1.2
2022-12-28T16:52:41+0100,main,583.5941,583.5941,583.5941,0.000073,0.0011,no error,5.0,8.0,3.4,6.1,9.0,4.0,1.2
2022-12-28T16:57:41+0100,main,583.5945,583.5945,583.5945,0.000080,0.0004,no error,5.0,8.0,3.4,6.0,9.0,4.4,5.3
2022-12-28T17:02:41+0100,main,583.5945,583.5945,583.5945,0.000000,0.0000,no error,5.0,8.0,3.3,6.0,9.0,4.5,5.4
2022-12-28T17:07:41+0100,main,583.5967,583.5967,583.5967,0.000440,0.0022,no error,5.0,8.0,3.3,6.0,9.4,6.6,7.9
2022-12-28T17:12:41+0100,main,583.5967,583.5967,583.5967,0.000000,0.0000,no error,5.0,8.0,3.4,6.0,9.4,6.6,7.9
2022-12-28T17:17:41+0100,main,583.6045,583.6045,583.6045,0.001560,0.0078,no error,5.0,8.0,3.4,6.1,0.5,4.4,5.0
 

Expected Behavior

No response

Screenshots

No response

Additional Context

No response

[TopGoalVl]

The problem also occurs in my system. I also use the version V13.0.8.

Remark:
The photos under: /log/source/yyyymmdd/hh/raw_*.jpg have a correct timestamp.

[caco3]

This should be fixed in #1839

[caco3]

Closing it as now as I did not get a feedback

[TopGoalVl]

It works for me in the current version. The issue can be closed. Thx.