The best thing you can get me is a log and find the path request that it got stuck on:
Code:
[05:43:42.630 D] Requesting path on 180 from <65.03135, 48.6017, -381.8394> to <23.94331, 28.1621, -776.2606>
These requests provide everything i need to know to investigate the issue, but there will be many of these in a log so unless your watching the bot it might be hard to find the right one. You can always try and reproduce the issue by stopping the bot, backing up and restarting the bot and see if it continues to derp.