In its initial implementation, Walk to Pokestop ignores pokemon along the way, so when the bot gets to the destination pokestop it merely retraces its steps back through the nests it discovered along the way in reverse order, so ends up back where it started and does nothing besides waste time for the initial walk since it did nothing along the way. What I think should happen is it should catch pokemon along the way so when it gets to the new pokestop it is ready to discover more in that area. Perhaps it should also spin close-enough pokestops along the way. Also, others have suggested that setting a new walk-to-pokestop destination should override the previous destination. I would argue that while overriding should be an option from the little popup menu, there is a reason to merely add a new destination as happens now, so a long path can be defined that takes turns and winds through various clusters of pokestops. This only makes sense if we are catching and perhaps spinning along the way, though.
