[Clarification] The timestamp arrival logic for Next MATR Cycle time starts <timeperiod> .

[Ziabatcha]

Version:V1.0.1.l_impl

Description
Please clarify the logic for timestamp arrival which prints at Next MATR Cycle time starts .The same pattern is not followed as per below logs.

Explanation from mail
Every Cyclic process are gapped by deviceListSyncPeriod.
<—Cyclic Process --> <-- Device sync period --> <—Cyclic Process --> <-- Device sync period --> <—Cyclic Process --> <-- Device sync period -->

But logs are not aligned as per above explanation.
Note:deviceListSyncPeriod "120" (2 hours) is setup in config file.

[04:00:00.006] INFO (1): MATR CYCLE START AT: 17/2/2026 04:00:00
[07:44:22.016] INFO (1): MATR CYCLE DURATION:03:44:22
[07:44:22.016] INFO (1): NEXT MATR CYCLE START AT TIME:Tue Feb 17 2026 08:00:00 GMT+0000 (Coordinated Universal Time)
[08:00:00.032] INFO (1): MATR CYCLE START AT: 17/2/2026 08:00:00
[11:34:14.755] INFO (1): MATR CYCLE DURATION:03:34:14
[11:34:14.755] INFO (1): NEXT MATR CYCLE START AT TIME:Tue Feb 17 2026 12:00:00 GMT+0000 (Coordinated Universal Time)
[12:00:00.032] INFO (1): MATR CYCLE START AT: 17/2/2026 12:00:00