Difficult to answer. The hardest question often starts by "sometimes" or "often". May be this page could help : Locality Perhaps AI leader(s) locality or the way your headless client works (if related to this topic)?  

pierremgi Are you sure that commands like [(_this#0),clientowner] remoteexeccall ["setOwner",2,false] always work ? or different question what are situations for dedicated when this commadn is blocked? from my experience command work god in 90% of cases but sometimes are AI units resistant for this command - stay remote no matter how you try to chenge their locality - any ideas what can cause this situation from dedicated logic what circumstances limiting apllying of this command on unit - on BI is nothing about this and problem is very offen observed?

Sorry guys but form all forum posts and my experience this command "setowner" might be bugged  from arma beginig - it sometimes work sometimes not on dedicated - sorry BI do nothing in this case from years - shame 😞

in my case it work in most cases but sometimes when I move to unit for capture it (joint to my group) using [(_this#0),clientowner] remoteexeccall ["setOwner",2,false] - this method not working at all, AI it stay remote forever and is no possibile to change it's locality to any other client, in WIKI is not any description when this command not affect on AI so how to find solution in this situation?

I have also problems with this command setowner by [(_this#0),clientowner] remoteexeccall ["setOwner",2,false] not working on some AI units on dedicted, sometimes some units stay still remote after apply this command and is no any logical explanation to it (unit is not used by any other client or HC on dedicated it only one client - me and this command not work on some units, for rest it working fine so WTF?? what are circumstances to block this translation by serwer any ansver from BI possibile??