Move to Location, AI Move To, Simple Move to Location - are always 0,0,0 velocity in first frame

Current solution is to check distance to Destination Location in Tick.
If I am close enaugh to Destination, run “Alternative Finish Action” - which call “Move To” another location. So, I have smooth movement without break for one frame.

But this is HACK, I should not do this. Every “Move To” should not be broken.
Guys from EPIC maybe don’t know it is a bug ?