bug / unexpected behavior

[hyvokar]

Hi!

Just run in to this one.
If you have a backup sheduled to start daily at 05:00 and allowed backup window set to 05:00-06:00 and you when change your backup to start at 04:00 ; your backup will never run. Expected behaviour would start the backup at 05:00. However, in this case the "next run" value is changed to 1.1.0001 0:00:00, when it should be current/next.day 05:00:00

[foggy]

Expected behaviour would start the backup at 05:00.

It is not an expected behavior. You've scheduled the job to start at the time it is not allowed to start, so it will not even attempt to run.

However, in this case the "next run" value is changed to 1.1.0001 0:00:00

This is a bug indeed, it should state "Not scheduled", will be addressed in future versions.

[hyvokar]

It is not an expected behavior. You've scheduled the job to start at the time it is not allowed to start, so it will not even attempt to run.

I still dont get it why it wouldn't start at 05:00 . Also, Now when the job is never run, you wont get even an error message telling you that something is wrong.

[foggy]

It wouldn't run, since you've specified time it is not allowed to run at. Job start time should be in the allowed time, the job doesn't wait for the allowed time to come.

[Gostev]

Moreover, the job will be automatically stopped, should it be started earlier and then get into the time slot where it is not allowed to run.

[hyvokar]

This is a bug indeed, it should state "Not scheduled", will be addressed in future versions.

Make it in bold red font, so even I'll take note of that