Task manager in async mirror behavior

Hello,

We had a weird behavior of task manager in mirror async backup-failover pair:

1. server 1 was primary, server 2 backup for over a month, as there was no automatic failover (switch) both had IRIS up for over a month
2. We manually switched making server 2 primary
3. The tasks that had this issue were set to "run on Primary only"
4. Task manager started to execute tasks every minute: we noticed that "Next scheduled time" is always calculated in past date, and progressing by the task interval (e.g. a task that supposed to run every hour will have "Next scheduled time" in the past e.g. 2025-04-17 18:00:00 then after run will be 2025-04-17 19:00:00 and so on (we see this behavior for all tasks regardless of the interval (every 5 min, 30 min, 1 hour, x hours etc.)

Seems that the "Next scheduled time" is calculated also in the past, which might be a bug.
I know that %SYS.TASK is not mirrored (%SYS) so there is no sync. Also, not an option to map this to another DB.
I also don't want to maintain another mirrored global with last time for each task (ugly workaround).
Another option I was thinking is to auto set all tasks "Next scheduled time" on mirror change (auto or manual) using the ZMIRROR, but again its an ugly workaround.

Anyone know any good workaround or fix for that behavior?