Is there a way to allow tasks to fail? I have the following setup:

@dynamic
def base_workflow(config: Config):
    for i in [1..10]:
        task_a = a(i=i)
        task_b = b(i=i)
        task_c = c(i=i)
        task_a >> task_b >> task_c

This all starts nicely 10x in parallel (as desired), but as soon as one of the tasks fail (lets say, task_a fails for i=3), they all abort. Is there a Flyte-native way to allow i=3 to fail, but let the others complete?

For a workflow you can set a failure policy, to allow remaining tasks to continue.

@workflow(failure_policy=WorkflowFailurePolicy.FAIL_AFTER_EXECUTABLE_NODES_COMPLETE)

That sounds great, unfortunately

@dynamic

doesn’t have that field, but maybe I can find a way to nest a workflow or something to use it.

Setting it on the top level should propagate it downward, so if you wrap your dynamic in a workflow that should work out

Works! Thanks a lot @rapid-vegetable-16315 🙌

we also encountered this, would be nice to add that field to the

dynamic

decorator as well...

Maybe you know this as well @rapid-vegetable-16315 @quaint-diamond-37493 since you're also working with dynamic tasks/workflows: Is there a way to add a prefix/label/name to the tasks, instead of the rather cryptic

n1-0-dn3

etc.? That would be nice to quickly see on first glance in the UI on what item a failure occured (ie. did it fail on

i=1

,

i=2

, ..?), without having to go into the Inputs

@shy-evening-51366 I have not investigated this, but you may be able to use something like

a(i=i).with_overrides(node_name=f"a: i={i}")

This is demonstrated as above in docs about subworkflows (which I realize is different than the above use-case, but may still work for you).

Thanks @microscopic-furniture-57275! Interesting, it seems it picks up the names when the task did not run yet. When they are running/have completed, they switch back to a random identifier: