Some tasks have a tendency to break (I am thinking specifically of data processes reliant on shaky third party APIs) but it may be difficult to properly account for all of the potential errors ahead of time and make sure your task can survive it. In this situation, it can be helpful for Dagobah to automatically retry your job up to a certain number of times before giving up and declaring the task a failure.
I think we need to do three things:
Add a user-configurable maximum number of times to retry a Task, set at the Task level
Add a property on the Task object that tracks how many times the Task was retried during its last run. This will end up in the run log.
Patch the existing email templates to show task retries.
Some tasks have a tendency to break (I am thinking specifically of data processes reliant on shaky third party APIs) but it may be difficult to properly account for all of the potential errors ahead of time and make sure your task can survive it. In this situation, it can be helpful for Dagobah to automatically retry your job up to a certain number of times before giving up and declaring the task a failure.
I think we need to do three things: