Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Store error details on failure #40

wants to merge 2 commits into


None yet
6 participants

jcoene commented Feb 17, 2012


In migrating from Redis, one feature I found missing was the inclusion of error details with failed jobs. I've found this to be preferable to using Airbrake/Exceptional in a project where the success of a job can't be guaranteed.

The attached changes to the Mongo backend store errors along with the failed job. It also ensures they aren't included on requeue.


bkeepers commented Feb 17, 2012

Thanks for the pull request! Let me think about this for a day or two. I agree that it's nice to have, but I want to think through what it means for the other backends and if there's better way to do it.

jcoene commented Feb 17, 2012

Sure thing, just give the word if I can help! Thanks for the awesome project.

👍 it would be a good thing to have

This would be a great inclusion... did the merge ever happen, or is Qu development currently stalled?


jnunemaker commented Dec 23, 2013

Looks like requeue has been removed so this is out of date. I could see this being handy for mongo, though I'm inclined to say that it would be better to just make a mongo failure backend than to add it to the job here.

@jnunemaker jnunemaker closed this Dec 23, 2013

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