Loïc Mathieu 5c24308e71 fix(executions): evaluate multiple conditions in a separate queue ...

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

2025-10-03 10:35:49 +02:00

..

src

fix(executions): evaluate multiple conditions in a separate queue

2025-10-03 10:35:49 +02:00

build.gradle

chore(system): extract the scheduler to its own module

2025-09-04 11:04:13 +02:00