Sidekiq: How can you enable the ability to see Failed jobs like you can inspect the "Dead" queue?
Why is this not clickable?
Other than process, it's literally the only link on the top bar that isn't clickable. Sometimes I want to see what jobs have failed without having to wait for them to appear in the dead queue or having them programmatically going there right away.
bobber205
All 7 comments
Failed jobs are "retries" in Sidekiq. Don't disable retries.
mperham
on 28 Jan 2015
We're currently only specifying retries = 0. Does this prevent it from going straight to the dead queue?
bobber205
on 28 Jan 2015
Jobs with retry = 0 should die and go to the morgue immediately if they fail.
mperham
on 28 Jan 2015
@mperham The behavior is correct, but still we should be able to know what was the reason for failure so that we can fix it and retry that worker right, meaning, just like retrying job, we can see the details, why can't we see details of failed jobs.
userrails
on 14 Jan 2019
You can see the error that caused a Dead job.
mperham
on 14 Jan 2019
@mperham the issue is that when sidekiq_options retry:false, there is no way of knowing why some jobs failed. In my case i have over 80K jobs running in a hour at times. And so if a job fails it would be nice to come back and see the reasons as to why some specific job out of the 80K that failed. If this cant be added, alternative i will built some other notification mechanism anyways
mistaguy
on 27 Aug 2019
The Error Handling wiki page discusses best practices and trade offs. I don’t have anything further to add unless you have specific questions.
On Aug 27, 2019, at 07:09, Acellam Guy notifications@github.com wrote:
@mperham the issue is that when sidekiq_options retry:false, there is no way of knowing why some jobs failed. In my case i have over 80K jobs running in a hour at times. And so if a job fails it would be nice to come back and see the reasons as to why some specific job out of the 80K that failed. If this cant be added, alternative i will built some other notification mechanism anyways
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
mperham
on 27 Aug 2019
Related issues
smanolloff
·
3Comments
homanchou
·
3Comments
mperham
·
3Comments
sandstrom
·
3Comments
bartimaeus
·
3Comments
Most helpful comment
@mperham The behavior is correct, but still we should be able to know what was the reason for failure so that we can fix it and retry that worker right, meaning, just like retrying job, we can see the details, why can't we see details of failed jobs.