Should I Log A NA?

[+CacheWolfy]

There's a local cache around here, which I found a while ago. When I was passing the cache area, I looked in the same spot, and it was gone. I spent a few more minutes looking around, to no avail. This actually was a quite easy cache to find, good quality container and waterproof. I logged a NM after 2 other DNF's and the CO did not do anything. After 2 other DNF's, what should I do? I do know the cache owner in real life, before geocaching, so I told him, but still nothing has happened. Thank you! =)

GC Code is: GC5T74A

[+Ben0w]

Yes, a NA is appropriate here. Give details, just like in your posting - including the fact that you already talked to the owner.

 

Depending on the personality of the owner it may give a bit of hassle, but it's a pretty clear NA situation. The owner still has time to do maintenance, even after NA is posted. Most probably the reviewer will give some weeks before archiving. Even after that, the owner has some days to perform maintenance and get the cache from archive. So, it's just a bunch of warnings, no need for anger. A non maintained geocache is a greater pain.

Edited August 1, 2015 by Ben0w

[+colleda]

Yes, a NA is appropriate here. Give details, just like in your posting - including the fact that you already talked to the owner.

 

Depending on the personality of the owner it may give a bit of hassle, but it's a pretty clear NA situation. The owner still has time to do maintenance, even after NA is posted. Most probably the reviewer will give some weeks before archiving. Even after that, the owner has some days to perform maintenance and get the cache from archive. So, it's just a bunch of warnings, no need for anger. A non maintained geocache is a greater pain.

Yes, log NA as it's been over a month since the NM. This will bring it to the reviewers attention. It will then be disabled for a month and, if still no action from CO, it'll be archived.

[+L0ne.R]

Yes log the NA. Enough time has passed since your NM. I suggest that you preface your log with "Needs attention". Perhaps say: "Needs attention. I found this cache before and can confirm it's missing. Perhaps it can be temporarily disabled until the cache owner can replace or archive the cache."

[+cerberus1]

If you're comfortable logging an NA (knowing the CO) it's seems due, but you did tell him already.

To me, logging an NA after logging an NM , then personally telling him looks like an agenda.

If it bugs you that much (you started a thread here...) maybe an email to the Reviewer would be a better, drama-free bet.

Complete replacement its first month, now missing just another month later, maybe they're realizing this hiding part of caching's not so hot and are discussing what to do.

Still logging in, if they can't take care of their only hide, it should go.

Edited August 1, 2015 by cerberus1

[+Manville Possum]

Yes, log NA on the cache.

[+Inmountains]

Whether there is an "agenda" or not, if the cache is gone AND the Cache Owner is no longer active, just log the "NEEDS ARCHIVED." There is a high probability that the CO doesn't even open his/her emails from Geocaching if they are no longer active.

[+cerberus1]

Whether there is an "agenda" or not, if the cache is gone AND the Cache Owner is no longer active, just log the "NEEDS ARCHIVED." There is a high probability that the CO doesn't even open his/her emails from Geocaching if they are no longer active.

The OP gave the GC#, so we can see the CO is active and found a cache today.

[+baloo&bd]

The OP gave the GC#, so we can see the CO is active and found a cache today.

 

All the more reason to post NA, CO is ignoring issue.

[Pup Patrol]

There's a local cache around here, which I found a while ago. When I was passing the cache area, I looked in the same spot, and it was gone. I spent a few more minutes looking around, to no avail. This actually was a quite easy cache to find, good quality container and waterproof. I logged a NM after 2 other DNF's and the CO did not do anything. After 2 other DNF's, what should I do? I do know the cache owner in real life, before geocaching, so I told him, but still nothing has happened. Thank you! =)

GC Code is: GC5T74A

 

The cache owner isn't responding for a reason?

 

If you have told him in person that there is a problem, and there's been no action, then go ahead and log the NA.

 

The DNF's should have been enough to get him out there to check on it. So he's had plenty of notice that there is a problem.

 

B.

[+narcissa]

Logging an NA is totally up to you.

 

Looks like the CO was "inactive" for a few weeks. Sometimes people have other things going on. Maybe give this person the benefit of the doubt and wait a bit longer? A couple of months really isn't a big deal.

[+CacheWolfy]

Ah, matinence has been performed, everything is fine.

[+Cachez]

I've recently had the same thing. I logged a cache as NM on 1 August because the container was missing with all the bits left on the ground and also emailed/messaged the owner. No response, and it looks as though they might be inactive so today I stuck an NA on it. I get irritated with COs where there are numerous DNFs and NMs which seem to go unnoticed.

 

GC3Q8V5 for example has had nothing but DNFs since the beginning of May, yet nothing has been done.

Edited August 24, 2015 by Cachez

[+edexter]

Logging an NA, especially after a month or so of no response to an NM, makes sense. About 3% of caches are missing at any given moment. The only way to get a missing cache "off the books" is for somebody to archive it. When the CO is unresponsive, only The Reviewer can do that and in my area only a NA gets The Reviewers attention. When you post an NA log the CO has five responses they can make with little effort: continue to ignore it, post an OM log or note saying "it's fine" or "I'll fix it soon", disable the cache so folks know it's unlikely to be there, archive it, or delete your log. Some respond with a combination of two or more. If you are specific enough in the reason you are posting the log you might get action sooner rather than later. For instance, one of the recent NA logs I posted noted the cache had not been found in 11 months, there were 7 consecutive dnfs, and the CO hadn't responded to 2 NM logs. The CO almost immediately deleted my log and disabled the cache saying they'd get to it soon and The Reviewer put it on their "watch list". So a good outcome. An abandoned cache would get no response and eventually get archived.

[Pup Patrol]

I've recently had the same thing. I logged a cache as NM on 1 August because the container was missing with all the bits left on the ground and also emailed/messaged the owner. No response, and it looks as though they might be inactive so today I stuck an NA on it. I get irritated with COs where there are numerous DNFs and NMs which seem to go unnoticed.

 

GC3Q8V5 for example has had nothing but DNFs since the beginning of May, yet nothing has been done.

 

The CO of GC3Q8V5 may very well have received the new Maintenance Email from Groundspeak. There's no way of knowing, though.

 

edit: never mind, GC3Q8V5 has been archived.

 

Don't forget that Groundspeak started sending out "Maintenance Emails" back in September 2015.

 

http://forums.Groundspeak.com/GC/index.php?showtopic=334834

 

Help Center → Hiding a Geocache → Geocache Ownership: A Long-Term Relationship →

4.9. New Maintenance Emails from Geocaching HQ

 

Geocaching HQ sends occasional emails to geocache owners when it appears that a geocache needs maintenance. The emails may result from any combination of logs, including Did Not Find (DNF's), Needs Maintenance (NM), Needs Archived (NA) or caches that have not been found in a long time.

 

If the cache owner is not reading the logs, the emails from when a cache has been logged, or the Maintenance Email from GS, and is not responding in any way on the cache page, then a "Needs Archived" is justified.

 

Responding to the NA logs I've posted, the Reviewer has disabled caches and cited the non-response to the "Maintenance Email" from GS. The cache owners get yet another chance to do something.

 

No action or response from the cache owner in 30 days = Archived.

 

B.

Edited December 12, 2015 by Pup Patrol