I noticed that MC-124124 was marked resolved when what I believe was the actual culprit behind it went unresolved. A failure on part of the users to identify the actual problem or a failure to articulate it. What I ran into and spent a whole night trying to work around was exactly this problem. Only one workaround "fixed" the problem and it was that case that showed why it was happening. The entity in question here was summoned with the following command: /summon minecraft:arrow ^ ^ ^ \{CustomName:"\"WandRay\"",CustomNameVisible:1b,NoGravity:1b} Note that it can be any entity, just easier to see with straight line entities like the arrow and trident. Considering this command: /execute rotated as @p at @e[name=WandRay] run teleport @e[name=WandRay] ^ ^ ^ facing ^ ^ ^-1 As I understand it, it should run teleport at the entity 'WandRay' with the orientation of the player. Since Z-1 is forward direction in view space, this should cause the entity 'WandRay' to rotate but not translate. Specifically it should re-orient the entity 'WandRay' to match the player's orientation.  Note that 'WandRay' is trying to change orientation. If you get close to the entity and pay attention,it has a slight twitch to it where it twitches a degree or two clockwise then snaps back to it's original orientation. It does this repeatedly after running the command, in my test case for 3 hours before I was convinced it would continue to do so endlessly.  Consider altering the command to the following: /execute rotated as @p at @e[name=WandRay] run teleport @e[name=WandRay] ^ ^ ^0.01 facing ^ ^ ^-1 This works but it changes the position of the entity which is a problem for some use cases. So the workaround became run the following commands: /execute rotated as @p at @e[name=WandRay] run teleport @e[name=WandRay] ^ ^ ^0.01 facing ^ ^ ^-1 /execute rotated as @p at @e[name=WandRay] run teleport @e[name=WandRay] ^ ^ ^-0.01   All of this was ran in a single player super flat creative world but it doesn't seem isolated to just that type of world.