Closed BobReid closed 1 year ago
As far as I can tell this is a typo in the template unless I am missing something.
I put up a PR for a potential fix. https://github.com/rq/django-rq/pull/590
Just doing a little more digging in the Django RQ source code. This may be an incompatibility with the RQ version we are using and the latest version of django-rq.
Am closing this out as I have confirmed upgrading RQ fixes this issue.
Issue:
Failed jobs that end up in the FailedJobRegistry do not display the stack trace in django admin. django-rq version 2.7.0 rq version 1.7.0
Screenshot of current details template