Building on what Len wrote here, it’s not quite accurate that we “can’t figure it out.” A better statement would be that it happens infrequently enough that it’s not worth the time it would take to resolve this issue. At some point we will overhaul the personalized touring plan interface, and we’ll likely fix it then.
As another poster here suggests, the bug is related to time zones, but it’s not related to anything that you (as someone experiencing the problem) did, so you cannot take a different action to avoid the issue. Generally speaking, though, if you create a plan and end up with weird meal/break start times, you’ll be able to go in manually and fix those times without incident.
The 31-minute cookie issue that started this thread is unrelated to the 3-hour “time zone bug.” I would need to look at the specific plan (which no longer exhibits the problem) to figure out what was going on there. Although I think wolfing down a carrot cake cookie in 5 minutes would be a bad idea, our software isn’t smart enough to know that.