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
2024-10-22T03:00:00.245294425Z stderr F 2024/10/22 03:00:00 processing thing with ID 59e50053-0d33-4729-9732-9e69ade399a2
...
2024-10-22T03:00:00.414909773Z stderr F 2024/10/22 03:00:00 processing thing with ID 59e50053-0d33-4729-9732-9e69ade399a2
Version
gocron: 2.12.1
Expected behavior
The task should be run only once.
Additional context
I have tested the scheduler behavior locally and the NextRuns method of the job returned what is expected.
The text was updated successfully, but these errors were encountered:
EDIT: Since I am using Gocron to add jobs to a queue, I was able to temporarily fix this by adding a constraint to the queue to not accept duplicate inputs created at the exact same timestamp.
Describe the bug
It seems this long standing issue (see #52, #132, #159, and #601) is still unresolved.
I have configured a daily job running at 3:00, which processes a batch of entities relevant to my domain. The job completes in around 170ms:
but this occurred last night:
Version
gocron
: 2.12.1Expected behavior
The task should be run only once.
Additional context
I have tested the scheduler behavior locally and the
NextRuns
method of the job returned what is expected.The text was updated successfully, but these errors were encountered: