Currently if a job throws any exception we catch it and simply set the state of the job / task / target to FAILED :/
It is hard to determine why the job has failed and we should provide more information in the UI.
This will likely mean taking the exception type and message and shoving them somewhere in the DB alongside the failed state object.
Hmm. Careful here. Some sites consider it a security risk to expose exception details to users.
Currently the failure exceptions get logged into the 'massaction' log.
Need some way to expose more details to the use though, perhaps just exception names to start with, and depending on the type of exception otherdetails about the message could be given.