This is because the problem lies outside of the LookAt Function and is based upon where it is being called/what’s being passed in/how often. I see it’s being called from “Interaction Trace” but that itself is also a function which must be called, so we need to go up further in the chain of events. Where is “Interaction Trace” being called? Tick? If so, changing it to only be called on when asked may be the answer. It’s possible tick is restarting the logic at different points in the execution line here.
Looking a little closer I notice your “Content” array of structs is being Replicated. Is that intentional? This could be a new thread to follow for the issue, you could have the server and client fighting over what’s correct. I’m not sure about that one, though, it’s just a thought because it seemed out of place.