What happened?
The loop_mode column exists on #__workflow_transition_automation, and the language strings describe it as "Chain to Next Rule; after running, immediately chain into the automation rule of the target stage." Nothing reads the column at runtime. Setting it has no effect.
Impact
A user-facing setting that appears functional and does nothing. Anyone who enables it will reasonably expect chained transitions and get silence, with no error to explain why.
Options
- Implement it; but the semantics need defining first: does chaining re-evaluate the target stage's rules immediately, or on the next scheduler run? What prevents an infinite loop between two stages that each chain to the other?
- Remove it; drop the column, form field and language strings until the behaviour is actually wanted.
Given the loop-safety question is unresolved, removing it and reintroducing it deliberately is probably the cleaner path. Whichever is chosen, it should not ship in its current state.
Version
5.4
Expected result
No response
Actual result
No response
System Information
No response
Additional Comments
No response
What happened?
The loop_mode column exists on #__workflow_transition_automation, and the language strings describe it as "Chain to Next Rule; after running, immediately chain into the automation rule of the target stage." Nothing reads the column at runtime. Setting it has no effect.
Impact
A user-facing setting that appears functional and does nothing. Anyone who enables it will reasonably expect chained transitions and get silence, with no error to explain why.
Options
Given the loop-safety question is unresolved, removing it and reintroducing it deliberately is probably the cleaner path. Whichever is chosen, it should not ship in its current state.
Version
5.4
Expected result
No response
Actual result
No response
System Information
No response
Additional Comments
No response