I think this comes from a well known bug in the movements. I have correctedf it for next beta.
The bug is due to changing the movement within a collision event. To avoid the problem, set a variable to a value depending on the movement wanted, and changed the movement when testing the counter.