Geert07/07/2023, 11:55 AM
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?
@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
Maarten de Jong07/07/2023, 12:03 PM
Geert07/07/2023, 12:08 PM
doesn’t have that field, but maybe I can find a way to nest a workflow or something to use it.
Maarten de Jong07/07/2023, 12:09 PM
Geert07/07/2023, 12:12 PM
Felix Ruess07/07/2023, 1:06 PM
decorator as well...
Geert07/07/2023, 6:28 PM
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
, ..?), without having to go into the Inputs
Thomas Blom07/07/2023, 9:38 PM
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).
Geert07/10/2023, 10:13 AM