You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Singleton jobs can fail to get rescheduled due to a channel error causing the executioner to never rerun the job and raise no error.
There is a race condition in the executioner which causes a singleton job to not get re-scheduled properly.
The error is in the executioner pushing a job to the jobIDsOut channel (executor.go line 180)
There seems to be an issue where there is something already in the channel, therefore it is skipping placing the job in the channel via the "default" case.
Removing the default case fixes the issue.
To Reproduce
Steps to reproduce the behavior:
Run a overlapping gocron job in singleton format with LimitModeReschedule. Example:
Describe the bug
Singleton jobs can fail to get rescheduled due to a channel error causing the executioner to never rerun the job and raise no error.
There is a race condition in the executioner which causes a singleton job to not get re-scheduled properly.
The error is in the executioner pushing a job to the jobIDsOut channel (executor.go line 180)
There seems to be an issue where there is something already in the channel, therefore it is skipping placing the job in the channel via the "default" case.
Removing the default case fixes the issue.
To Reproduce
Steps to reproduce the behavior:
Version
Latest Version (v2.2.4)
Expected behaviour
Job should be re-scheduled
Additional context
The text was updated successfully, but these errors were encountered: