max_attempts reached, failed_at remains nil #422

resistorsoftware opened this Issue Aug 3, 2012 · 0 comments


None yet
2 participants


delayed_job (3.0.1)

I set the max_attempts to 2 on a job. I raise an error in the perform, trap it with a hook, and then watch what happens. I check my Delayed Job table, and sure enough, I get 2 attempts. I also get 2 failure exceptions recorded by Airbrake, so all is well.

Now, I want to clean out these kinds of failed jobs, and the documentation states the failed_at timestamp should be set non-nil? once the max attempts are reached. I am seeing this attribute remain set to nil.

Is that the expected behaviour? I am curious becuase while it is nice to know jobs failed, I also want to remove the ones that have based on some reliable criteria and I guess I misinterpreted the docs on the failed_at timestamp... any thoughts?

@albus522 albus522 closed this Sep 24, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment