We're updating the issue view to help you get more done. 

scheduled tasks shouldn't stop running after an exception

Description

_emphasized text_at the moment, if there is an exception running a scheduled task, it's flagged invalid and silently stops working, the only indication is that the task is listed in the administrator as invalid.

this means any minor network outage, a dependent service being restarted or some random error will cause a scheduled task to stop running.

Users should reasonably be able to assume a scheduled task will always be run according to the schedule and the current behavior doesn't match that.

It would also be very useful to store the last exception against the task and list that in the administrator under scheduled tasks, rather than requiring the user to go and dig into the logs to work out why a scheduled task isn't working.

Environment

Status

Assignee

Michael Offner

Reporter

Zac Spitzer

Labels

Sprint

None

Fix versions

Priority

Blocker