Version
v5.56.8
Platform
NodeJS
What happened?
Hello,
When a repeatable job's repeatJobKey contains 5 or more colon-separated segments, the worker falls into updateRepeatableJob instead of updateRepeatableJobMillis that creates ghost duplicate schedulers instead of correctly deduplicating them.
I believe it comes from worker.js (line 816), causing it to create a new scheduler entry instead of updating the existing one.
I shortened my keys to stay under 5 colon segments and manually deleted the old schedulers from my database. It seems to work as the issue has not reproduced since.
Is this behavior normal or am I missing something ?
How to reproduce.
Create a jobScheduler with more than 4 colon segments.
Let the worker pick up and process the first job.
After processing, the worker calls repeat.updateRepeatableJob() instead of jobScheduler.upsertJobScheduler()
On the next tick, there are 2 jobs.
Relevant log output
Code of Conduct
Version
v5.56.8
Platform
NodeJS
What happened?
Hello,
When a repeatable job's repeatJobKey contains 5 or more colon-separated segments, the worker falls into updateRepeatableJob instead of updateRepeatableJobMillis that creates ghost duplicate schedulers instead of correctly deduplicating them.
I believe it comes from worker.js (line 816), causing it to create a new scheduler entry instead of updating the existing one.
I shortened my keys to stay under 5 colon segments and manually deleted the old schedulers from my database. It seems to work as the issue has not reproduced since.
Is this behavior normal or am I missing something ?
How to reproduce.
Create a jobScheduler with more than 4 colon segments.
Let the worker pick up and process the first job.
After processing, the worker calls repeat.updateRepeatableJob() instead of jobScheduler.upsertJobScheduler()
On the next tick, there are 2 jobs.
Relevant log output
Code of Conduct