Job Retries Configuration Are Not Respected

[devhammed]

Hello there,

Thank you for the work on this package, but the worker does not respect the specific job retries configuration, no matter how I configured it:

Now, if you look at this error, you can see the context has 4 attempts instead of failing on the first execution as expected:

And another context is this error message when I enabled NODE_DEBUG:

You can see the worker is still seeing the global maxRetries setup instead of the one on the job.

Another issue you can notice is that the original error that happened is lost forever because what is passed to the failed method is E_JOB_MAX_ATTEMPTS_REACHED, which does not have any information whatsoever about the original error.

[RomainLanz]

Thanks! Fixed and released under 0.3.2.

[devhammed]

Thanks! Fixed and released under 0.3.2.

Thank you for the quick fix. Is there a plan to provide the original error that caused the E_JOB_MAX_ATTEMPTS_REACHED error?

I know error objects have the cause property, if you can pass the error there, it will be very useful!

[RomainLanz]

Thanks! Fixed and released under 0.3.2.

Thank you for the quick fix. Is there a plan to provide the original error that caused the E_JOB_MAX_ATTEMPTS_REACHED error?

I know error objects have the cause property, if you can pass the error there, it will be very useful!

0.3.3 👌🏻