Unexpected email notification for an old log...

1.7k · August 1, 2016

On Saturday 30/07/2016 I received an email notification of a Found It log on an archived and locked cache which I have on a Bookmark List

The log was dated 03 Nov 2002

I thought maybe the cacher had found a way to log it and had made a backdated log but this does not appear to be the case because the 'GL' codes immediately before and after it have the same date.

Probably not worth investigating but I just thought I would mention it...

M

7.3k · August 1, 2016

On Saturday 30/07/2016 I received an email notification of a Found It log on an archived and locked cache which I have on a Bookmark List

The log was dated 03 Nov 2002

I thought maybe the cacher had found a way to log it and had made a backdated log but this does not appear to be the case because the 'GL' codes immediately before and after it have the same date.

Probably not worth investigating but I just thought I would mention it...

M

It would probably be a lot easier for someone to check into if the GC code was supplied.

B.

August 1, 2016

It would probably be a lot easier for someone to check into if the GC code was supplied.

Yep. People, don't be so general in your posts, these things (caches, logs, TBs... user accounts as well) are public so why not include the identificator of what you are referring to.

13.8k · August 1, 2016

It would probably be a lot easier for someone to check into if the GC code was supplied.

Yep. People, don't be so general in your posts, these things (caches, logs, TBs... user accounts as well) are public so why not include the identificator of what you are referring to.

Sounded (to me) as a ruse to have something, "probably not worth investigating", into something that now needs to be investigated.

1.7k · August 1, 2016

It would probably be a lot easier for someone to check into if the GC code was supplied.

If anyone who could check wanted to check they would ask me.

I wondered if anyone else had had a similar experience.

M

22.1k · August 1, 2016

Please provide the GC Code, since you are posting in the website bugs forum. It's not possible to do anything with your report without investigating.

11.7k · August 1, 2016

What is the GC Code?

1.7k · August 1, 2016

Please provide the GC Code, since you are posting in the website bugs forum. It's not possible to do anything with your report without investigating.

Okey-doke

The GL code is GL16YGP

The preceding GL code: GL16YGN the following one: GL16YGQ are both dated with the same date which suggests that the log has been in the system for a long, long time.

M

11.7k · August 1, 2016

So the GC Code is GCA087.

August 1, 2016

That is weird. I can confirm that based on what I can see, the log was made back in 2002, it isn't recent and that does mesh with the coords.info information you posted.

I know there have been some recent hiccups in the matrix lately so it is possible it is related to that.

5.7k · August 1, 2016

It would probably be a lot easier for someone to check into if the GC code was supplied.

If anyone who could check wanted to check they would ask me.

I wondered if anyone else had had a similar experience.

M

Yes. Even archived caches can be logged if 'found' if the finder can determine the gc code, and if a newly found archived cache is on one of your lists for which you're being notified, you're going to get a notification.

Example: I had a DNF that I returned to and found. Turns out the cache had been archived two days earlier. Since it was on my watch list, I got a notification of my own find.

1.7k · August 2, 2016

Yes. Even archived caches can be logged if 'found' if the finder can determine the gc code, and if a newly found archived cache is on one of your lists for which you're being notified, you're going to get a notification.

Example: I had a DNF that I returned to and found. Turns out the cache had been archived two days earlier. Since it was on my watch list, I got a notification of my own find.

How about reading the ENTIRE thread BEFORE commenting??!!!! :rolleyes:

Edited August 2, 2016 by Delta68

1.7k · August 2, 2016

I have ALL the old Locationless caches on a bookmark list and set to receive notifications.

I received another email yesterday on another cache - GC5569 this time.

Once again, it was a log from 2002 logged at that time as well.

M

August 3, 2016

I can confirm this is happening as well. I received a notification for this log on a locked virtual cache at 7:53am this morning.

Edit: Double checked and I also received a notification for this log as well, on 7/29/16 at 2:14 PM.

Edited August 3, 2016 by Pine and Poplar

1.5k · August 3, 2016

I was just notified of a 3 Nov 2002 log on a Locationless.

https://coord.info/GL17034

Have all the old logs been from 3 Nov 2002? seems like it...

1.7k · August 3, 2016

I was just notified of a 3 Nov 2002 log on a Locationless.

https://coord.info/GL17034

Have all the old logs been from 3 Nov 2002? seems like it...

That's a very interesting observation!

The notification I got for GC5569 (https://coord.info/GL16ZFF) was dated October 26th 2002 but looks like it was actually logged on November 3rd 2002 as the logs either side are (GL16ZFE and GL16ZFG ) are both dated November 3rd!

M

5.7k · August 4, 2016

Yes. Even archived caches can be logged if 'found' if the finder can determine the gc code, and if a newly found archived cache is on one of your lists for which you're being notified, you're going to get a notification.

Example: I had a DNF that I returned to and found. Turns out the cache had been archived two days earlier. Since it was on my watch list, I got a notification of my own find.

How about reading the ENTIRE thread BEFORE commenting??!!!!

My, aren't we friendly?

For others who might be reading this thread, and since your early post asked "I wondered if anyone else had had a similar experience.", and since it has happened to me in the past, a positive response with an explanation seemed in order. YOURS is not the only case where this can occur. Those searching for answers that run across this thread in the future might benefit from other possible explanations for such an event.

1.7k · August 4, 2016

My, aren't we friendly?

Sometimes...

For others who might be reading this thread, and since your early post asked "I wondered if anyone else had had a similar experience.", and since it has happened to me in the past, a positive response with an explanation seemed in order. YOURS is not the only case where this can occur. Those searching for answers that run across this thread in the future might benefit from other possible explanations for such an event.

EVERYONE knows it's possible to log finds on archived caches which is what your example was.

Logging finds on LOCKED caches is rarer

Being notified of finds logged on caches nearly 14 years ago was unheard of until very recently.

M

5.7k · August 4, 2016

Actually, 'everyone' doesn't know that it's possible.

Another thought...

We know that the system will won't permit a new log entry on a locked cache, but can a user EDIT a previous log on a locked cache, and what results? One would not expect a new notification to go out to those with the cache in a list under such circumstances, but having never tried to edit a log on a locked cache ... ???

A lot of folks have been editing their prior logs en masse with a variety of tools to pull out BB Code and replace with this new 'markdown' stuff.

Even similar caches (GCC859) which one might expect to be locked are only archived. I don't know that I've found any that are now locked so that I could try to edit my log to see what happens.

22.1k · August 5, 2016

Logs on locked caches can't be edited. And, edited logs don't trigger notifications. So, it's likely that edited logs are not triggering these mystery notifications.

7.4k · August 5, 2016

I can't be sure, and the developer who recently worked on the new notification service is not currently available, but I believe he mentioned that he discovered a backlog of old messages in the queue that had been "lost" by the old service. I recall him mentioning the possibility that the new service might pick these up and deliver them, much later than expected. It is possible that this might be what is occurring in these cases.

22.1k · August 5, 2016

But insta-notify didn't exist in 2002, when these logs were initially recorded. :unsure:

EDIT: Duh! I was focused on "Published" notifications only. There are also watchlist emails, which were a feature in 2002.

Edited August 19, 2016 by Keystone

6.8k · August 5, 2016

But insta-notify didn't exist in 2002, when these logs were initially recorded.

I seem to recall to have watched some caches in the early times and to have to have received watch list mails. According to my memory one received mails in November 2002.

Edited August 5, 2016 by cezanne

13.8k · August 5, 2016

Guess I don't get it...

Why are locationless included in notifications anyway?

1.5k · August 6, 2016

I received another email for another 3 Nov 2002 log on a locationless GC9876.

https://coord.info/GL170T7

Like Delta68, this would evidently be coming from a bookmark list, not from a notification (though I appreciate there may be little to no difference from the coding side).

To cerberus1 - when notifications were new, a Locationless could have all logs posted that are the basis of notifications EXCEPT publish:

Found it Didn't find it

Temporarily Disable Listing Enable Listing

Write note Post Reviewer Note

Update Coordinates

Needs Archived Archive Unarchive

Needs Maintenance Owner Maintenance

Publish Listing

I appreciate that most users set up only Publish notifications. The bulk of mine are for archive and retract.

Edited August 6, 2016 by palmetto

August 6, 2016

I received another log notification dated 11/1/2002. This one was on a virtual that is archived but not locked. The log itself appears to have been deleted by the owner, but the owner hasn't logged in since 2005.

"Wow - what a view! This was an incredible climb up for us, only to find it locked and no ranger in site. We took a picture of the lock (utbob2 will send) so we hope that counts. Still, a heck of a climb and an incredible view."

1.5k · August 12, 2016

I continue to receive notification of found logs on Locationless. The date range has expanded to include Nov 1,2 and 3 of 2002.

I assume this is tied up in the issue of current notifications (mostly of publish logs, my assumption) being buggy.

August 15, 2016

I just received a notification for this 11/4/2002 log. I was not watching the cache at the time, and in fact did not even join GC until a few years later. The logging member (an elderly couple) have not logged on to the web site in three years and have not logged a find in five years, and no one knows if they are even still alive. I'll be happy to supply the message source if that will help.

EDIT: I already had that log in GSAK, so I know it didn't change, at least not visibly.

Edward

Edited August 16, 2016 by paleolith

1.4k · August 15, 2016

Groundspeak have developed a time machine and are testing it.

August 16, 2016

I have bookmark lists of all archived caches in Australia and set to receive emails for any posts on all of them.

I have received a number of emails for logs in 2002 in the last 24 hours. I can give GC codes if required...

At least one of these caches was locked.

I have all of the caches in my GSAK database and have checked and the logs were in the Database prior to my emails so it looks like they are somehow GC is sending delayed emails for postings back in 2002.

August 16, 2016

I can't be sure, and the developer who recently worked on the new notification service is not currently available, but I believe he mentioned that he discovered a backlog of old messages in the queue that had been "lost" by the old service. I recall him mentioning the possibility that the new service might pick these up and deliver them, much later than expected. It is possible that this might be what is occurring in these cases.

That's an interesting information for this other bug...

I wouldn't want to be the guy who messed up the instant notifications before going on holiday once he returns...

Sorry for the interruption

August 19, 2016

got a bookmark notification for this log: https://coord.info/GL174J7 yesterday. This log has already been archived (probably years ago).

According to the email it is a log from november 5th 2002

August 19, 2016

It's really weird that it's not just random logs popping up out of the grave. It's only logs from early November, and perhaps late October, of 2002. And though the log PnavE81 cited may have been on an archived cache, the one I cited was on a still-active cache. (Which is why I watch that cache.)

Edward

7.5k · August 19, 2016

It's really weird that it's not just random logs popping up out of the grave. It's only logs from early November, and perhaps late October, of 2002. And though the log PnavE81 cited may have been on an archived cache, the one I cited was on a still-active cache. (Which is why I watch that cache.)

I wonder if these are being sent because the system thinks it's sending one of the notifications on a new cache, i.e., the notifications that are missing. These all seem to be old caches, so perhaps it's being caused by an overflow in an index calculation.

August 19, 2016

It's really weird that it's not just random logs popping up out of the grave. It's only logs from early November, and perhaps late October, of 2002. And though the log PnavE81 cited may have been on an archived cache, the one I cited was on a still-active cache. (Which is why I watch that cache.)

Edward

The log is archived. The caches is still active. https://coord.info/GC2B36

So far all logs posted in this thread are from november 1-5 2002

1.5k · August 21, 2016

Today I received notification of a 11/05/2002 log on a Locationless.

I report this, as I assume it's related to the notification problem generally, which apparently is not yet resolved.

August 23, 2016

I received another log notification on a locked virtual (GC3009) from 11/3/2002 about half an hour ago. Apparently this bug is still active in the system.

1.5k · August 28, 2016

I continue to receive these. Now I'm getting most as duplicate emails:

[LOG] Bookmark: IT-gubben found Väderkvarnar/windmill (Archived) (Locked) (Locationless (Reverse) Cache)

2.7k · August 29, 2016

Groundspeak have developed a time machine and are testing it.

Will this be another platinum member perk?

August 29, 2016

I continue to receive these. Now I'm getting most as duplicate emails:

[LOG] Bookmark: IT-gubben found Väderkvarnar/windmill (Archived) (Locked) (Locationless (Reverse) Cache)

[LOG] Bookmark: IT-gubben found Väderkvarnar/windmill (Archived) (Locked) (Locationless (Reverse) Cache)

surprise surprise...IT-Gubben found this one on 7 november 2002 (https://coord.info/GL1776T)...another log from the beginning of november 2002

August 30, 2016

Just a heads up that this is on our radar and we are investigating. Our present-day selves are not working on a time machine, but I can't speak for our future selves. Perhaps Geocaching HQ is using the notification system to communicate with ourselves in the past (which is our present). And no - we don't have anyone on staff named John Connor.

1.5k · August 31, 2016

Groundspeak have developed a time machine and are testing it.

Will this be another platinum member perk?

If you were, are, or were ever going to be a platinum member, you wouldn't need to ask that question.

September 1, 2016

I am sorry to disappoint everyone, but it turns out the issue was not related to a time machine after all. The issue has now been resolved and notifications from the past should no longer be delivered.

Unexpected email notification for an old log...

Recommended Posts

Join the conversation