How much longer should we wait?

[3 Hawks]

I’ve noticed more than a few caches in the area that have been in a “Temporarily” disable status for up to seven months and running. Most of them were disabled because the cache went missing and most of them included promises to get the cache up and running ASAP.

Well most of them have not been reactivated and just sit there excluding sometimes usable space.

I know there can be any number of reasons why a cache owner does not get a cache back in play quickly, but most responsible cache owners post notes or something to let people know the status and to explain delays.

I know I can flag cache posting to be ignored so they don’t keep popping up on my searches, but when is enough time, enough time?

What do you think is a reasonable amount of time a cache should sit in a disabled status with no posted notes before it should be archived? What is your opinion of cache owners who do not respond to friendly e-mails on their caches status but throw a holy fit as soon as you post a please archive note?

[The5Xplorers]

Like which caches? Are any of them in the Cache Rescue list?

[PCFrog]

This admittedly is something that I don’t like to see as well. Here are the GC.com regs/rules/ guidelines

“As the cache owner, you are also responsible for physically checking your cache periodically, and especially when someone reports a problem with the cache (missing, damaged, wet, etc.). You may temporarily disable your cache to let others know not to hunt for it until you have a chance to fix the problem. This feature is to allow you a reasonable time – normally a few weeks – in which to arrange a visit to your cache. In the event that a cache is not being properly maintained, or has been temporarily disabled for an extended period of time, we may archive or transfer the listing.”

I had bad luck in the past just simply asking a owner their status with the cache so generally I just send a little FYI to a reviewer so they can officially post a notice to an owner. Some reason in my experience most owners get pissed when you ask about their 4+ month temporarily disabled cache.

The reviewers and very good at following up on these as well.

[The5Xplorers]

It’s too bad people can’t take care of what they put out there. Going through the reviewers is the best way to go in my opinion.

[GOJeepers]

I recently posted a “Needs Archived” note on a cache that had been temporarily disabled for 7 months, saying they had picked the cache up and would relocate. Within hours, a reviewer had posted a message saying it would be closed in 4 days if it wasn’t resolved by then. The owner then abandoned the cache area and admitted they had moved so it wasn’t convenient for them anymore. It was all very civilized and handled quickly. Makes me wish I had done it sooner, then maybe I would have had a new cache to put out for the Geo Campout last weekend. 🙂

I think anything more than 1-2 months of being “temporarily” disabled is excessive and anyone should feel free to post a maintenance or archive note to get the reviewers involved.

Sara

[3 Hawks]

@The5Xplorers wrote:

Like which caches? Are any of them in the Cache Rescue list?

It has been a while since I posted a “please archive” request and each time I did I got a nasty response even after countless attempts to contact the owners.

The caches I’ve had my eye on recently are “Horseshoes, anyone? (GCXQ9Q) and Tree Hugger (GCVJCF). They have both been “temporarily disabled” since October. I think 7 months is about long enough for anyone, except under extreme circumstances, to at least find someone else to do that which they pledged themselves.

I don’t want people to think I’m a horse’s ass, but irresponsibility is just one of the things that gets under my skin. I’m sure each of the owners has seemingly valid excuses (I mean explanations) for the delay, but wouldn’t it then be proper to at least post a note?

[Buy_The_Tie]

Have a look at the Long Disabled Cache Cleanup policy. I have gotten a little behind due to the campout.

Now that we are past the campout and we are 3 reviewers strong, rest assured that I will be back at it.

[bandits]

@Buy_The_Tie wrote:

Now that we are past the campout and we are 3 reviewers strong, rest assured that I will be back at it.

WOW! Just looked at the recent logs and you are most definitely back at it. Talk about afterburners! Thanks for all the hard work!

[Ms. WISearcher]

I know that we have one that is temp. disab. in Madison, and it is not because the cache isn’t maintained, but rather there is construction downtown which could make it unsafe to complete…so we temp disab until the construction is done…which could be a while. There are many reasons that a temp is dis.

good question though!

[3 Hawks]

There are a few around Milwaukee that are disabled for the same reason and one is disabled for another safety issue. The owners posted timely notes to inform the community of their issues and I see nothing wrong with these caches remaining in a ‘temp dis’ status until the area is clear and/or safe.

On the other hand, we have some caches in temp dis status where nothing appears to be wrong aside from no updates after the initial “I’ll get this cache up and running ASAP.” Seven months later; no further updates.

Don’t promise that which you either can’t deliver or have no intention of delivering. It all comes down to responsible and courteous communication.

[Author]

Posts