Open focusaurus opened 9 years ago
i dont think is module is designed for emails. don't email services have their own queueing systems? its more for map/reduce jobs where you want to save the output, and if it errors, you can just run it again (which you're going to do anyways).
however, retries is something i do want to add. right now, you'll look for jobs that are .processed
and have a .error
Yes, they do, but that doesn't help when you can't connect to email services or they are throwing retry-able errors.
Based on the README it's not clear if this module allows for a job to fail and be retried later, and if so, how metadata about that failure (like connection refused when trying to send an outgoing email) should be recorded. Or is your thought that as far as the queue is concerned, the attempt is the job and if that fails, noting that failure is up to the app and the app should dispatch a retry job into the queue?