Assigning a keybinding to move a window to the Next screen moves it one screen to the left while Previous moves it to the right which is counter intuitive. (Atleast on my system)
that's because you have your screens backwards. the bindings change screen count by 1 or -1 ... screens are numbered based on which is primary or not (0) as well as the priority value in the screen setup - highest priority is sorted to start of screen count. if priority is the same then it's in order of x value .... then y value for screen location.... :)
Oh that makes it even more buggy and fun if you don't start on the center screen. I have 2 - 1 -3 (74-100-0) if I start at 3 and go one way it just swaps between 2 and 3, (for maximised windows) maybe it should look at if the screen is leftof or rightof other screens and put together an order.
but that's not what the action does - it shuffles up and down by screen number which is dictated by priority. it's NOT a "move window left or right one screen" which would do what you want. :) we don't have such actions... :)