Feature request: Timed manual runs #7

When manually running a job a time should be selectable. The would allow triggering a manual run which will actually be run hours later (eg. unplanned scheduled sync)

Why do we need this?

We need this because sometimes we want to trigger a manual run. However, jobs can trigger performance issues. So triggering them at night should be a better way to go. However, humans are no vampires and sleep at night.

Design

The basics for this are already there. For reboot jobs the database field running is set to the timestamp of when get services command should be run. When setting this for other jobs this currently triggers a fatal error as this is not being reset and will trigger a run over and over and over. This last issue should be covered.

When manually running a job a time should be selectable. The would allow triggering a manual run which will actually be run hours later (eg. unplanned scheduled sync) ## Why do we need this? We need this because sometimes we want to trigger a manual run. However, jobs can trigger performance issues. So triggering them at night should be a better way to go. However, humans are no vampires and sleep at night. ## Design The basics for this are already there. For reboot jobs the database field `running` is set to the timestamp of when get services command should be run. When setting this for other jobs this currently triggers a fatal error as this is not being reset and will trigger a run over and over and over. This last issue should be covered.

Labels Milestones

Feature request: Timed manual runs #7

Why do we need this?

Design