Travel bug in wrong cache

[+scenic explorer]

I have done a very silly thing!!

I dropped off a travel bug but logged the drop in the wrong cache. The only problem is i didnt make note of the code.

 

Does anyone know how i can change the travel bug drop to the correct cache? I feel so daft.

[+Ambient_Skater]

If you didn't have the code how did you log it into the wrong cache in the first place?

 

Ask the owner of the bug for the code and explain the situation. Then delete your erroneous log and drop it in the right cache.

[+TheFamilyYoung]

If you didn't have the code how did you log it into the wrong cache in the first place?

 

Ask the owner of the bug for the code and explain the situation. Then delete your erroneous log and drop it in the right cache.

 

I've never needed a code, I dropped a TB off today and whilst I was on the new cache page, I selected 'found it' and the TB that was in my possession showed also with a dropdown that enabled me to drop it off whilst on the cache page. If I'm doing something wrong someone tell me? The TB is showing as being in the new cache so presumably that's OK?

[+Bear and Ragged]

You need the TB's unique number -from the tag- to Retrieve the TB from the cache, once it's in your inventory you only need to select it when you write a log -or note- to Drop it in a cache.

[+mpilchfamily]

I have done a very silly thing!!

I dropped off a travel bug but logged the drop in the wrong cache. The only problem is i didnt make note of the code.

 

Does anyone know how i can change the travel bug drop to the correct cache? I feel so daft.

Return to the cache and write down the TB's code. The log it into the correct cache.

[+luvvinbird]

I have done a very silly thing!!

I dropped off a travel bug but logged the drop in the wrong cache. The only problem is i didnt make note of the code.

 

Does anyone know how i can change the travel bug drop to the correct cache? I feel so daft.

Return to the cache and write down the TB's code. The log it into the correct cache.

Welcome to the club. I goofed once myself only I had to find my way back through two feet of snow. A lesson learned. In any case, go to your room and no supper!

[+TomToad]

Email the owner of the TB and explain what happened. The owner might then email you the code so you can grab it back from the wrong cache and place it in the correct cache.

[+The Blorenges]

There's a chance that your pc may have cached the tracking code in the TB box...

 

Go to any trackable that you've logged recently, click on "Found it, log it", then just left click your cursor in the tracking code box: You may find it gives you a drop-down list of the tracking numbers that you've entered recently - My pc gives me the last 12 numbers. Make a note of those numbers and use them to bring up the various trackables - It may be that one of them will be for the TB which is in the wrong cache.

 

Once you've identified which it is you can then use the tracking number to remove the TB from the "wrong cache" and then do a Note to drop it into the correct cache.

 

It's worth a try

 

MrsB

[+roziecakes]

If you didn't have the code how did you log it into the wrong cache in the first place?

 

Ask the owner of the bug for the code and explain the situation. Then delete your erroneous log and drop it in the right cache.

 

I've never needed a code, I dropped a TB off today and whilst I was on the new cache page, I selected 'found it' and the TB that was in my possession showed also with a dropdown that enabled me to drop it off whilst on the cache page. If I'm doing something wrong someone tell me? The TB is showing as being in the new cache so presumably that's OK?

 

They would need the code to retrieve it from the erroneous cache to then drop into the correct one. The poster who said to email the owner, is the best option you have.

 

If you don't hear back from the owner, you could make a note on the cache pages of the two caches explaining the situation to the next finders, and whoever picks up the TB can log it as "retrieving it from somewhere else."

 

You get points for honesty!!

[+Mark+Karen]

I have a similar issue, I did note down the tracking number but must have noted it down wrongly as it doesn't accept it. So now I'm stuck, I've emailed the CO but no reply.

[+Gitchee-Gummee]

I have a similar issue, I did note down the tracking number but must have noted it down wrongly as it doesn't accept it. So now I'm stuck, I've emailed the CO but no reply.

In this case.... play with the tracking number. You have the proper sequence, now you need to "guess" which digit you copied incorrectly.

 

1=I; 2=Z; 0=O=Q; 8=B; sometimes even D=0; there are more confuse(able) digits.

[+A & J Tooling]

Okay, let's say, for instance, that 'someone' picked up 3 travel bugs and placed them in 3 caches but that someone might of logged them in the wrong ones but the only way to know for sure is to actually go back there and check. That is not feasible. What now?

[+luvvinbird]

Wouldn't a worse case (but do-able) scenario be to just leave them where they are and let the next person to find them enter the correct numbers and get them back in the game?

[+Gitchee-Gummee]

Okay, let's say, for instance, that 'someone' picked up 3 travel bugs and placed them in 3 caches but that someone might of logged them in the wrong ones but the only way to know for sure is to actually go back there and check. That is not feasible. What now?

Any more "what-ifs" you'd like to toss up?

If logging travelers properly is that difficult for 'someone', 'someone' probably should stick to moving no more than one at a time.

 

The occasional goof-up is gonna happen. But if one puts oneself in a logistical nightmare trying to shuffle and move travelers, I would think they would want to re-think the "recreational" part of geocaching.

 

The system was made just a bit simpler a while back by allowing one to log a traveler into a cache with one single log, instead of logging the find, then logging the traveler separately. I think keeping a little note (fieldnotes, or personal notebook) to keep track of the multitude of drops in a single outing is a pretty easy solution.

[+Gitchee-Gummee]

Wouldn't a worse case (but do-able) scenario be to just leave them where they are and let the next person to find them enter the correct numbers and get them back in the game?

Yes, that would be one way of doing it. Certainly not a method that you will catch us using. Sorry, but I find no honor or conscience in such a maneuver. If I goof-up, I fix-up....

 

At this juncture, I'd best stop typing....

[+BlueDeuce]

Okay, let's say, for instance, that 'someone' picked up 3 travel bugs and placed them in 3 caches but that someone might of logged them in the wrong ones but the only way to know for sure is to actually go back there and check. That is not feasible. What now?

 

Post a Note on the cache and the bugs explaining that it may not be logged in the right cache. If so instruct them to Grab it away and 'visit/dip/drop-and-retrieve' in the right cache and continue on.

 

Start carrying a little notebook and writing down your transactions. You should already be writing down the tracking numbers until you know you have successfully logged the bug into the right cache. Trust me, it'll happen again so you better be prepared. It's what I do.

[+SurveyContactTeam]

Start carrying a little notebook and writing down your transactions. You should already be writing down the tracking numbers until you know you have successfully logged the bug into the right cache. Trust me, it'll happen again so you better be prepared. It's what I do.

Good heavens, I'm glad I read this post! I picked up my first TB from a cache recently and it never occurred to me that I might not be able to depend on the online info to help me keep track of its number until I put it in a new location. I have now written down all the relevant info into my little notebook. Just in case. Thanks for the advice!

[+BlueDeuce]

Start carrying a little notebook and writing down your transactions. You should already be writing down the tracking numbers until you know you have successfully logged the bug into the right cache. Trust me, it'll happen again so you better be prepared. It's what I do.

Good heavens, I'm glad I read this post! I picked up my first TB from a cache recently and it never occurred to me that I might not be able to depend on the online info to help me keep track of its number until I put it in a new location. I have now written down all the relevant info into my little notebook. Just in case. Thanks for the advice!

 

Not only that, now you can share your knowledge and help others as well. It's all part of Happy Caching.

 

See you on the trail.

 

BD

[+sheddybetty]

Okay, let's say, for instance, that 'someone' picked up 3 travel bugs and placed them in 3 caches but that someone might of logged them in the wrong ones but the only way to know for sure is to actually go back there and check. That is not feasible. What now?

 

Is it really not feasible? If not, post a note to each cache that the TBs might have come from and ended up in and explain that you would like anyone that comes across these TBs to post a current position for them. Email each of the TB owners and COs. The TB owners know which cache it came from because, to them, it still looks like it's there. What you want right now is to inform the TB owners that their bugs are currently off the radar and what you are trying to do to help them.

 

Lastly (and from now on firstly) write down the code on the TB you find in the future. You need that to log your find and it informs the owner, and anyone else who's interested, of where it is.