hyvokar wrote:Expected behaviour would start the backup at 05:00.
hyvokar wrote:However, in this case the "next run" value is changed to 1.1.0001 0:00:00
foggy wrote: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.
foggy wrote:This is a bug indeed, it should state "Not scheduled", will be addressed in future versions.