Welcome to the Forums. I have to admit, I’m slightly struggling to follow your logic but it would seem that this being on tick is the problem.
From what I can tell when you start AIMoveTo in the StartMovingToBowl function you must be setting bIsMovingToBowl to true which would make the next tick jump to the False path of that branch which would set the CurrentState enum back to Idle which would then make the switch go back to idle which would reset the bIsMovingToBowl and that would continue around and around in a circle breaking your logic. They aren’t firing at the same time but on tick they are happening fast enough that it appears that way that’s why all those execution paths are highlighted.
Not being able to see all your logic I can’t say for sure but from what I can tell this should not need to be running on tick (The times when you need to run anything gameplay wise on tick rounded to the nearest whole number is 0, if you need repeating behaviour use timers). Functions like AIMoveTo are letent (denoted by the little clock in the top right corner) this means they happen over time anyway so if you call it again while it’s still running it will not work right.
Again I may be missing some info here and am giving you incorrect information but I am pretty confident that is the problem.