Everything an edge condition can see — the SUPERSET of both dialects.
A flow condition is written against payload / stepResult / flowContext / data / context;
the dispatcher's own conditions are written against status / succeeded / failed / output /
errorMessage. Compiling flows onto this engine without the flow dialect would make every
payload.x condition evaluate against nothing — silently, since an undefined property is simply
falsy. Both dialects are readable here so a condition means the same thing on either engine.
payload is the ORIGIN task's post-step snapshot. There is deliberately no "graph-wide payload":
each task's output is its own, and inventing a merged one would give conditions a value the flow
engine never had.
Everything an edge condition can see — the SUPERSET of both dialects.
A flow condition is written against
payload/stepResult/flowContext/data/context; the dispatcher's own conditions are written againststatus/succeeded/failed/output/errorMessage. Compiling flows onto this engine without the flow dialect would make everypayload.xcondition evaluate against nothing — silently, since an undefined property is simply falsy. Both dialects are readable here so a condition means the same thing on either engine.payloadis the ORIGIN task's post-step snapshot. There is deliberately no "graph-wide payload": each task's output is its own, and inventing a merged one would give conditions a value the flow engine never had.