Hi,
I find three tracks to investigate:
It could be that your robot controller stopped the trajectory (it tries to complete the motion during a short time until the trajectory gets out of reachability or so). What's your robot? Do you know what is your controller? Do you have feedback from it? Velocities and/or efforts could be too high for it, in particular if you see jumps in IK between two points. A proper jump_threshold value should avoid that (but may imply a lower % of success).
Since the beginning of the trajectory is wrong it would suggest that you are not using the good reference frame, but since visualization in RViz is ok I would not favour this track. However it's easy to check with a
setPoseReferenceFrame()
Also I'm not sure what move() and execute() do exactly, but according to the doc, move() = plan() + execute(), so I would execute() the cartesian trajectory in your case, instead of move(), since that method could replan to a goal formerly defined.
Cheers,
Yoan Mollard
Research engineer – 3rd hand project

INRIA Research center, Flowers lab