handler is called even when there is retry logic added to the Task, and the task still hasn't exhausted its
max_retries
. (I think I just had a Task on which the
on_failure
handler was called, even though it succeeded in a retry.)
Is there a way to add a failure handler that is called only after the task has exhausted all its retries and has truly failed?
k
Kevin Kho
05/19/2021, 2:39 PM
Could you give me a minimum reproducible example for this one?
p
Peter Roelants
05/19/2021, 3:12 PM
I circumvented the issue by switching to Triggers instead of using
on_failure
k
Kevin Kho
05/19/2021, 3:16 PM
Oh ok thanks for letting me know. We were looking into this and you’re right because the task goes from Running -> Failed -> Retrying and the failed hits the state handler.
👍 1
p
Peter Roelants
05/19/2021, 3:18 PM
Thanks for letting me know that you also run into this.
I thought this was unexpected behavior, and was surprised by it.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.