[Bug]: Repeatable job is not fired off immediately after it's removed and added back

[raymondfeng]

Version

v4.14.0

Platform

NodeJS

What happened?

Hi, I noticed a strange behavior. We have a repeatable job. If we remove it or drain the queue for delayed jobs and add it back with immediately=true , the workers are not fired off.

How to reproduce.

1. Create a queue and add a repeatable job with immediately=true option
2. Create worker for the queue to handle the repeatable job
3. Remove the job or drain the queue
4. Add the repeatable job back to the queue with immediately=true option

The worker is not fired off immediately.

Relevant log output

N/A

Code of Conduct

• I agree to follow this project's Code of Conduct

[manast]

Could you please produce the actual source code that reproduces the issue?

[fabianboerner]

For use this issue occured when the original repeated job was still in completed and not completely removed from redis. If you remove the delayed job after the original it will not add another job.

[manast]

This is probably fixed with the new upsertJobScheduler method. @fgozdz could you verify it indeed is resolved?