#3861·conductor

[FEATURE]: Idempotent task execution within fork.

Author: dimiturPavlovskiCreated Nov 24, 2023Updated Dec 8, 2023
Labelstype: feature

Describe the Feature Request

Looking to have the capability to ensure idempotent parallel execution of tasks within a fork. It should be an alternative to the default fail-fast approach where, if a task fails within a fork, the other tasks get cancelled. The cancelled state causes problems on our side as it is a not deterministic state and the cancellation logic creates race conditions where other tasks within the same fork might get executed or might not. download

Describe Preferred Solution

Describe Alternatives

We have a customer facing feature, that allows customers to define tasks as being optional or not. So for achieving idempotent execution of tasks within a fork we cannot leverage optional as it is reserved. Some tasks in the fork may be optional, or may not be optional. If not optional, we would like those to not interrupt the other tasks prior the join. Upon join, if any non-optional failed, we need to fail the join.