Direct synchronous execution refuses a workflow that loops
The engine walks the compiled order once and never re-enters a node, so it cannot iterate a loop. It refuses the workflow rather than running the body once and reporting success.
The rule
Normative: this is the rule
- Direct synchronous execution walks the compiled execution order once, top to bottom, carrying results in memory, and never re-enters a node.
- After compiling and before any node executes, it checks the compiled graph for loopback edges; where any is present it refuses the run with a distinguishable refusal that names the offending edges and nodes and points at the strategies that do iterate, and no node executes.
Why
Recorded under OPEN-13.
Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · ORC-7 · changed in spec 1.0