logging Travel Bugs

[+Happy Hikers]

We recently placed a TB in a cache and before we could enter it someone grabbed it, logged it as grabbing from us and placing again in the same cache, grabbing it again and therefore getting credit for it. Not that I really care about numbers, but was interested in the mileage as we brought it from CA to IN. Can this be corrected and what is protacol when a TB can not be logged immediately?

[+BlueDeuce]

It didn't get logged through a cache it visited? If you still have the tracking number yes it can be corrected. What bug is it? (Use the reference number located in the upper left of the bug page)

[+Eartha]

The bug got the credit, but they didn't get the credit for dropping it.

 

You have to email the person who grabbed it from you, and see if they will delete their log, and allow you to place it in the cache. You'd have to have the tracking number from the tag, grab it back , and drop it in that cache, then they have to retreive it from the cache. If all you want to see are the miles from CA to IN, then look at the bug page.

 

If neither of you still has the tracking number, you'll probably just want to leave it alone.

[+knitter]

That happens to us quite frequently - we drop a bug or geocoin when we're travelling from Point A to Point B, and before we get to Point B to log it someone has found it and grabbed it from us already. Seems some cachers have no patience. It's frustrating during long weekends, as sometimes we don't have a chance to log our finds and drops for a day or two due to travel and location, yet the finders won't wait until at least the Tuesday following a long weekend to give us the chance to log things. It used to be newbies who did this, but lately we've had this experience with long-term high-number cachers as well.

[+ncfinn]

Any time I drop off a TB knowing that I won't get to a computer for a day or two, I leave a note with it asking the next person to give me time to log my drop-off before logging his/her pick-up.