I have experienced several times that the scheduler, after completing one job, establishes a starting time for the next job a few seconds before the current time and then plans that job for the next day. See attached log file around time stamp [2024-03-13T00:07:24.919 CET INFO ] referring to job "Unknown" (I am using a reference image to plate solve the target location)

[2024-03-13T00:07:24.904 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Unknown \t03/15 00:03 --> 05:47 \taltitude 29.8 < minAltitude 30.0"
[2024-03-13T00:07:24.919 CET INFO ][ org.kde.kstars.ekos.scheduler] - "IC 410 \t03/14 23:10 --> 00:02 \taltitude 29.7 < minAltitude 30.0"
[2024-03-13T00:07:24.933 CET INFO ][ org.kde.kstars.ekos.scheduler] - "IC 410 \t03/14 20:11 --> 23:09 \tjob completion"
[2024-03-13T00:07:24.947 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Unknown \t03/14 00:07 --> 05:51 \taltitude 29.8 < minAltitude 30.0"
[2024-03-13T00:07:24.961 CET INFO ][ org.kde.kstars.ekos.scheduler] - "IC 410 \t03/13 20:10 --> 00:06 \taltitude 29.7 < minAltitude 30.0"
[2024-03-13T00:07:24.974 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Unknown \t03/13 02:25 --> 05:55 \taltitude 29.7 < minAltitude 30.0"
[2024-03-13T00:07:24.988 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Unknown \t03/13 00:07 --> 02:24 \tjob completion"

Read More...