Repeated "Path Failed" messages

Beginner Questions
1

I am seeing debug spew like the following:

Path Failed : Computation Time 0.00 ms Searched Nodes 0
Error: Couldn’t find a close node to the end point

I believe the same bad path is being attempted over and over again. I am not seeing the proper way for the code that started a pathfinding request to be notified the path is bad (so it can stop trying to follow it). What is the proper/recommended for game code to know the path failed and deal with it.

2

I’m using the OnPathDelegate call back (OnPathComplete from the tutorial) to check if a path is any good or not (for me a bad path is one where the endpoint of the path is unreachable) and then just added some logic to deal with the situation. Not sure what the “best practice” is but using the call back got me past a lot of errors.

3

Great, thank you!