Allow some jobs to be scheduled in the past #67

Closed
opened 2021-09-17 03:55:36 +00:00 by jamie · 3 comments
jamie commented 2021-09-17 03:55:36 +00:00 (Migrated from git.hazaar.io)

I have an issue where if I schedule an action to execute using @reboot from the main warlock.json config, by the time the schedule is added it is in the past and is rejected.

To fix this, I think it would be OK to allow jobs to be added that are scheduled in the past, but only up to the last 30-60 seconds.

I have an issue where if I schedule an action to execute using `@reboot` from the main `warlock.json` config, by the time the schedule is added it is _in the past_ and is rejected. To fix this, I think it would be OK to allow jobs to be added that are scheduled in the past, but only up to the last 30-60 seconds.
jamie commented 2021-09-17 04:20:08 +00:00 (Migrated from git.hazaar.io)

mentioned in merge request !38

mentioned in merge request !38
jamie commented 2021-09-17 04:20:08 +00:00 (Migrated from git.hazaar.io)

created merge request !38 to address this issue

created merge request !38 to address this issue
jamie commented 2021-09-17 04:20:33 +00:00 (Migrated from git.hazaar.io)

mentioned in commit efbc25a0c5

mentioned in commit efbc25a0c5e967bd7d5449ee250f95df4f8fb732
jamie (Migrated from git.hazaar.io) closed this issue 2021-09-17 04:20:33 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#67
No description provided.