Manually triggered job resulting in exception does not show up in monitor UI

[keeth]

I have a job that fails when it is run. When it runs at the normal interval triggered by the scheduler, the monitor plugin shows the exception, which is great. However if I trigger the job manually from the monitor page ("Run now") the error does not appear in the UI. When I refresh the page, or if another job runs causing a refresh, the error shows. So not a huge deal but would be cool to see the error right away if there is one.

[jamescookie]

Yeah, the problem is that when you trigger it manually (or by some other means) a temporary trigger is created. The job information (including errors) is stored against the triggers and so is lost in these cases. It would need quite a re-write to sort this out, but I'll think about it...