Repeatable Job Stuck in Queue Due to Past Timestamp Update

[divyesh565]

bullmq version - 5.1.5

For a repeatable job, what could be the reason that its next job timestamp is being updated to a past time, causing the job to never execute and remain in the queue indefinitely?

[manast]

If the timestamp is in a past time the delayed time will be zero and it will be executed directly, so we need more context to understand your case. Btw, I would upgrade to latest BullMQ version also.

[divyesh565]

We are inserting a job into the queue to repeat every 90 seconds. After some processing, we remove the job by its key. However, at the end of the day, when we check the queue in Taskforce, we see that there are X jobs with past timestamps for the 'next run at' field.

[manast]

We would need a test case to understand and to analize your issue in depth.