rough-rose-81585
09/15/2023, 6:33 PMtask
fail but still continue the workflow
? Our use case is a dynamic
workflow spawns N tasks
, and it’s ok if some small percentage fail. We’re currently using a try catch to return an empty result (likely could also use an Optional
), but then the user loses visibility by clearly seeing the task
as failed in the console.magnificent-teacher-86590
09/16/2023, 3:33 AMmap_task
over dynamic task that has success ratio parameters
• if its terminal then you can set the workflow failure policy so that rest of the dynamic tasks run to completion before workflow is marked as failedfreezing-airport-6809
magnificent-teacher-86590
09/16/2023, 4:37 AMfreezing-airport-6809
freezing-airport-6809
freezing-airport-6809
cool-lifeguard-49380
09/16/2023, 8:14 AM@workflow(failure_policy=WorkflowFailurePolicy.FAIL_AFTER_EXECUTABLE_NODES_COMPLETE)
but I have only ever used it with subworkflows that I wanted to be able to fail while others continue.rough-rose-81585
09/16/2023, 1:43 PMArrayNode map_tasks
and partial function map_task
support I think we need to start switching from dynamic
-> map_task
.
I believe both partial
and ArrayNode
are still experimental features. Would you recommend one over the other? It seems that ArrayNode
is the more long term solution? but it’s also newest only released in v1.9freezing-airport-6809
freezing-airport-6809
freezing-airport-6809
freezing-airport-6809
freezing-airport-6809
freezing-airport-6809
rough-rose-81585
09/16/2023, 1:44 PMrough-rose-81585
09/16/2023, 1:44 PM