Hey Tobias,
according to the Knowledge Base article it's yes but according to my tests a schedule restart doesn't solve the problem. You could check with this SQL statement (sorry couldn't test the MSSQL statement but Oracle works)
select
eh_ah_idnr, eh_name, eh_nextcheck, osa_starttime, eh_client, eh_tz
from
eh, osa
where
eh_oh_idnr = osa_oh_idnr
and eh_status < 1800;
select
eh_ah_idnr, eh_name, to_char(eh_nextcheck,'YYYY-MM-DD HH24:MI:SS') "NEXTCHECK", to_char(osa_starttime,'YYYY-MM-DD HH24:MI:SS'), eh_client, eh_tz
from
eh, osa
where
eh_oh_idnr = osa_oh_idnr
and eh_status < 1800;
If the error is fixed the "nextcheck" column should correspond to the schedulers period turn around date and time in utc.
For example. If the period turnaround is set to today 24:00:00 (midnight) the value of nextcheck should be "2019-04-01 22:00:00".
Hope that helps,
Matthias