Looking at the last part of the GIF where the bot stalls, the Combat —> Fly To execution path is repeatedly aborted and then re-activated, so “Fly To” barely gets a to run itself. We need to understand why your “DummyState” keeps switching rapidly between “Combat” and “Something else” (the GIF doesn’t show that part of your BT).
During initial testing it’s useful to turn on the debug visualizer in the Fly To node (under Debug Params -> “Visualize Optimized Path”). This will tell you exactly when paths are generated and what they look like. Also check your “Output Log” for any error messages from the navigation system.
I’m also curious to know what “FlightLocationKey” points to in your “Fly To” node, where are you setting it from and how often you’re setting it.