Bug
Chore scheduled in the past
Issue description
By deleting the next execution date for a chore, it should be paused. But after doing so, there is two jobs all of a sudden open for this chore.
Developer comments
The paused chore is reactivated by "topincs monitor" which recently was given the responsibility to check whether chores are healthy. For some reason the paused chore is not considered healthy.
Monitor recreated the job, due to a faulty dobject, which had a next execution date. Deleting the date in the form caused the job to be rescheduled in the past and was thus executed immediately. It should no longer be possible schedule chores for the past. The date should be bumped into the future automatically.
In the case at hand reminder emails were sent out whenever the chore was deactivated by deleting the next execution date in the form and saving. This should not happen and is more likely to be caught if the date is bumped into the future. When chore jobs are scheduled for the past, there is nothing the admin can do to catch the error.
|
Work sessions2
Start |
2022-04-20T09:01:18
|
End |
2022-04-20T11:09:43
|
Participant |
Robert Cerny
|
Start |
2022-04-20T12:47:51
|
End |
2022-04-20T14:28:32
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.