In case of several triggers setting a window monitor, it jumps between said monitors and stops randomly on one of them, which is inconsistent. Could you make it so that it at least always stops on the monitor of the bottom trigger or, better, only takes the last mentioned monitor as a jumppoint and doesn't jump everywhere?

I'm using 11.0.4, latest version, and issue persists. I have "Move to monitor 2.3" for all windows and "Move to monitor 2.4" for DisplayFusion afterwards, and it can jump to either of them, not strictly 2.4

Windows still jump
Also I noticed that if I manually create a script with basically a single line

it will be executed last no matter the order of triggers with innate "Move to monitor" function.

Test structure:
Trigger 1 (DF window): "Move to monitor 1"
Trigger 2 (any window): BFS.Window.MoveToMonitor(secondMonitorID, windowHandle);
Trigger 3 (DF window): "Move to monitor 3"

I want for them to launch in that strict order, so that even if the window jumps, it ends up on the third monitor.
However, triggers 1 and 3 apply still simultaneously, and trigger 2 applies last.
So, if I have triggers in any order, window will always end up on monitor 2.
If I disable second (manual) trigger, window will end up on either monitor 1 or 3, still inconsistent.