So, my kids and I set off our first travel bugs a week or so ago. One of my daughters has a travel bug that is now in Thunder bay and the distance travelled sounds about right. My travel bug is in BC, but it says that the distance travelled is 0.
Has anyone else seen this type of strange behaviour on the geocaching.com website? I sent in a problem request to the "support" people on the site, but they haven't even sent an acknowledgement email or anything.
I have gone to my travel bug page and clicked on the recalculate distance button, but it doesn't change anything.
I've noticed that it sometimes takes a few days before the mileage is updated on the website. It will also depend on how they logged the travelbug. I am assuming you are referring to you Swim Far Swim Fast TB. It's showing in the cache in BC, but I don't see the log where bscales dropped it there. They either deleted their log afterwards, or the bug page just hasn't been updated yet. I'd say give it a few days and see what happens. If it still hasn't been updated, you could try retrieving your bug and logging it back into the cache that it's in. Hopefully the mileage will show up then.
TASKForce3 wrote:So, my kids and I set off our first travel bugs a week or so ago. One of my daughters has a travel bug that is now in Thunder bay and the distance travelled sounds about right. My travel bug is in BC, but it says that the distance travelled is 0.
Has anyone else seen this type of strange behaviour on the geocaching.com website? I sent in a problem request to the "support" people on the site, but they haven't even sent an acknowledgement email or anything.
I have gone to my travel bug page and clicked on the recalculate distance button, but it doesn't change anything.
Yeah, travel bug stats are sometimes slow to update, although three days seems a bit much. Since you are the TB owner, and have the tag number (It'll be displayed in the top right of the TB page), you could try grabbing it from Haunted Hide, and then immediately place it back. (Use the "Write note" log option.) That might help. If you do try that, delete the cache note log when you're done -- The deletion won't affect the TB, and the log would just clutter the cache page...
Nothing in the Groundspeak forums about travel bug distance issues (and such issues do crop up, on occasion...)
I was able to fix it. I contancted the fellow who moved it and he dropped it into one cache, logged it in another cache and somehow got the system to not register the distance...go figure.
So, I grabbed it from purgatory and placed it where he says it actually is and all is well now.