mirror of
https://github.com/kestra-io/kestra.git
synced 2025-12-19 18:05:41 -05:00
By evaluating multiple condition in a separate queue, we serialize their evaluation which avoir races when we compute the outputs for flow triggers. This is because evaluation is a multi step process: first you get the existing condtion, then you evaluate, then you store the result. As this is not guarded by a lock you must not do it concurrently. The race can still occurs if muiltiple executors run but this is less probable. A re-implementation would be needed probably in 2.0 for that. Fixes https://github.com/kestra-io/kestra-ee/issues/4602