Manuel Astudillo

There are probably some edge cases in such an approach though, I have to think more about it.

With such an approach there is also the case where the job could get stalled (if the worker died in the middle of the processing for example), but sure, if...

Or even the case where the job is manually removed, in that case, there would be no more iterations.

I am going to close this one as it as it currently stands there is no action for us. If in the future there is an interest in implementing repeatable...

This would actually be relative easy to implement by having a TTL in the wait list, if when the job reaches the tip of the queue the TTL has passed...

Note: when discarding the job probably we want to actually move it to fail so that we can keep accounting of the discarded jobs.

@runningman84 BullMQ supports limiting the amount of jobs kept after completing or failing, is this not enough for your use case?

We do not have a function like that, however we have discussed in the past the possibility that a worker discards jobs that are over a certain age.

In practice it would have the same effect as what you need if I am not mistaken.

@antoniojtorres > The suggestion in [bull's issue 2522](https://github.com/OptimalBits/bull/issues/2522) by manast is workable, but would cause gaps in processing if there are thousands or more items that become stale. I do...