Recurring jobs sometimes run immediately when added to queue

[sbleon]

Sometimes, when I add recurring jobs to a queue, starting with a completely empty Redis, an instance of the job is immediately executed. Has anyone else seen this happen?

[manast]

Picture this: time is divided in slots separated by your repeating interval, the slots are fixed, they need to be so that all workers are in consensus on when the next repeatable job is supposed to be repeated. If you happen to add the recurring job very close to the next slot it will be executed directly.

[manast]

btw, this is also the way standard cron jobs works AFAIK.

[5achinJani]

I did see this in #305 but in my case the redis was not empty flushing it resolved it.

[sbleon]

Thanks, @manast . I somehow missed your timely response!

If you happen to add the recurring job very close to the next slot it will be executed directly.

If it is currently 12pm, and I schedule a job for 2am every day, that would not count as "very close to the next slot", right?

[manast]

@sbleon no, that would not count.

[roggervalf]

Closing as we support using immediately param