Difference in error behavior when a job is undefined about delayed HOT 4 CLOSED

@smudge
Hi, I have checked the recent 0.5.0 update.

Although undefined jobs are now retried, the rescheduling does not seem to be working properly for undefined jobs as a NameError is generated when job.max_attempts is referenced.

As a result, attempts value is not incremented and the job is retried indefinitely. Could you please check this?

from delayed.

Circling back! This behavior should be changed in the 0.5.0 release now.

from delayed.

Hi @daichi5! Thanks for the report, and good catch! You're spot on -- that job: section is redundant and unnecessary, and was not the result of anything intentional. The @job ivar is simply there to support memoization of the instance of the payload class, which we delegate method calls to so that API methods like max_run_time and max_attempts are honored by ActiveJob-executed jobs.

from delayed.

I thought one solution would be to not include the job key in the handler column. What do you think?👀

from delayed.