This is a classic example of the 'Base Point Bug" which is caused by an action acting directly on a base point parameter (in this case it is the Stretch1 action). To fix it, add a chained point/move on top of the base point parameter, Add the base point parameter to the new move action's selection set. Remove the base point parameter from the prior stretch action. Add the new point parameter to the stretch action's selection set. That 'insulates' the base point from the stretch action. The ONLY action that should act on the base point is the move that is associated with the chained point parameter. If you want to add any other actions that will affect the base point position, do not add the base point to those actions' selection sets. Add the chained point parameter instead.
