failed_at field is empty for the job in the DeadSet about sidekiq HOT 4 CLOSED

It can happen, two examples:

Jobs can be killed in the Web UI too.

from sidekiq.

Ok, so if we can parse the JSON like this:

job = Sidekiq::DeadSet.new.find { |c| !c["failed_at"] }
JSON.parse(job.value)

Also, I couldn't find a button on the UI and we can confirm that the job was not killed through the API, are there any other obvious reasons?

from sidekiq.

Those are the only reasons that come to mind.

from sidekiq.

Well, here is the answer. The job was super long-running and was killed as a poison pill after multiple retries. The reason found. Thank you for the ideas. Probably in that case it's correct that there is no failed_at attribute set for the job.

from sidekiq.