Brad Vogel
Brad Vogel
Can you share more about your use case for a job that retries an infinite number of times? Is it some recurring task?
Ok, and what's the "something" you do after the job is a success? Could that publish a new one-time job?
Yes, I would always create a new job for each task, eg calling an API once. By having a separate job per call, you'll know exactly what time the job...
Yes - is great!
+1 on ioredis. Excited for this update Lewis!
Try calling `save()` at the end, eg `job.delayUntil(Date.now() + DELAY_RETRY).retries(1).save()`
Thanks. Prs welcome :)
Yes, go for it! We switched our product's frontend from Backbone to React shortly after we wrote this module (and blogged about it here https://mixmax.com/blog/backbone-to-react-without-rewriting). So moving this to React...
cc @skeggse
I'm thinking the job since it's somewhat analogous to `retries`. However it makes the implementation a bit more complex since we have to store the `stallLimit` with each job alongside...