Closed Salakar closed 8 years ago
Hello, such feature is not planned since, most of the times re-delivery would create the same problem, and in general this problem is better solved by turning the job into an idempotent one. If instead the problem is avoid duplications of tasks at application level, I think it's up to the application data store to take the state. Can't see a good fit for this feature, but thanks for sharing it.
Another request, sorry! :smiling_imp:
Would be good to be able to do unique jobs, so a
UNIQUE
arg onADDJOB
perhaps, that checks if the job already exists in the specified queue (and job is queued or currently working?) and if so doesn't create it. Or perhapsADDJOBNX
.Thoughts?
Thanks, Mike