Closed manast closed 15 hours ago
Yes, we had a problem because we calculated the repeatable end date. The service parameter where changed and the enddate was calculated in the past. The result was the return value from queue.add was empty and we could not identify the error first.
https://github.com/taskforcesh/bullmq/pull/2574 it's covered by this pr
As it is easy to mistakenly add a job that has an old endDate argument that will result in a repeatable job that never repeats, it would be useful to throw an exception to make it aware for the developer that this is the case.