Bumping this - it’s not that the Groom is lagging behind, if you watch it frame by frame, it’s somehow ahead of the skeletal mesh it’s following.
I’ve been trying to debug this one myself, it’s not a case of “prerequisite tick” for ensuring that the Groom ticks after the skeletal mesh - I’ve already tried that one.
It’s certainly a bizarre bug, I’m not sure how the Groom would be projecting itself forward by 0.X seconds.
Don’t suppose you managed to find a solution to this?