LonelyCache

I don't know if it is because of the recent site updating problems or if it is just the way the system is supposed to work, but I have about 20 caches that I found on Feb 7 that have not shown up on my recent finds list. I did not log them until Feb 11 so that may make a difference. All caches that I have found since that date do show up.

afudc wrote:I don't know if it is because of the recent site updating problems or if it is just the way the system is supposed to work, but I have about 20 caches that I found on Feb 7 that have not shown up on my recent finds list. I did not log them until Feb 11 so that may make a difference. All caches that I have found since that date do show up.

The site update problems may have had an impact on this but things should be updating okay now. Since it has been over eight days since you found the caches, they will no longer be updated when you visit LonelyCache. They should however, be updated through the normal update processing. I don't know what caches you're missing, but if there are more than 30 found logs since your find then the normal update process will not include your finds. Are these finds near Yuma? If so, that may be why they haven't shown up since there was a lot of people in the area for the Yuma Mega Event.

Corfman Clan wrote:I don't know what caches you're missing, but if there are more than 30 found logs since your find then the normal update process will not include your finds. Are these finds near Yuma? If so, that may be why they haven't shown up since there was a lot of people in the area for the Yuma Mega Event.

I just took a closer look at this and yes, there are more than thirty finds posted after Feb. 7 and that is why your find isn't being included.

A cache will be scheduled for a full update 120 days after the last full update, so eventually your missing finds will be added. Each cache will resync all finds every 120 days so your finds will be added once the next full update is done.

These caches aren't even worth one point so I don't know if it's worth rushing the full update. If it is to you, then PM me a comma separated list of all the GC codes and I can force a full update.

Corfman Clan wrote:

Corfman Clan wrote:I don't know what caches you're missing, but if there are more than 30 found logs since your find then the normal update process will not include your finds. Are these finds near Yuma? If so, that may be why they haven't shown up since there was a lot of people in the area for the Yuma Mega Event.

I just took a closer look at this and yes, there are more than thirty finds posted after Feb. 7 and that is why your find isn't being included.

A cache will be scheduled for a full update 120 days after the last full update, so eventually your missing finds will be added. Each cache will resync all finds every 120 days so your finds will be added once the next full update is done.

These caches aren't even worth one point so I don't know if it's worth rushing the full update. If it is to you, then PM me a comma separated list of all the GC codes and I can force a full update.

As long as they will update at some point I am OK with it. Please don't do anything special. I am glad that you explained how the updates work.

Since the site has been live for just over a year, I figure it's time to check the counts again. Right now there are 115,406 caches, 9,964,042 found logs and 179,132 geocachers. That's an increase of about 14,000 caches, 1.9 million found logs, and 15,000 cachers in the past year. That's quite an increase, especially considering all the caches that have been archived too.

I've been noticing that newly found caches are no longer updating when I log into the site, but take until the next day. Is this a consequence of the changes with groundspeak?

Team Opjim wrote:I've been noticing that newly found caches are no longer updating when I log into the site, but take until the next day. Is this a consequence of the changes with groundspeak?

This would have been a problem when there was an issue validating your account with Groundspeak. That no longer is the case. Your recent finds are not updated when LonelyCache is in the process of updating its stats. The Groundspeak changes caused the stats not to complete one morning. The next morning there was another problem. That was fixed and the stats were updated the morning of the 15th. This morning there was an unrelated problem and the stats update did not complete. I'll reset things again tonight and hopefully the stats will update properly tomorrow morning. The upshot of all this is if the stats update didn't complete, then your finds are not updated.

Since we've begun a new year, LonelyCache currently has 119,919 caches, 10,771,923 finds and 190,739 geocachers. Wow!

It's been a long time since I've done this, but a little after four years from going live, LonelyCache currently has 160,676 caches, 17,967,654 finds, and 331,123 geocachers. Nice!

Those are some big numbers!

Congratulations.. that is quite an impressive run, keep up the great work and thank you for doing so !

In not quite three months since my last update, LonelyCache currently has 166,678 caches, 18,467,186 finds, and 337,980 geocachers.

Corfman Clan wrote:In not quite three months since my last update, LonelyCache currently has 166,678 caches, 18,467,186 finds, and 337,980 geocachers.

In the following week, Montana was added to LonelyCache so now LonelyCache has 174,500 caches, 19,039,297 finds, and 354,354 geocachers. Everything seems to be running fine with the increase too.

Earlier today, I made changes to include Idaho in LonelyCache. Before I turned Idaho on, LonelyCache had 174,889 geocaches, 19,112,694 finds, and 355,320 geocachers. That's not much of a change since the last report, but I wanted to snapshot the counts before any Idaho caches are added.

There seems to be an update problem again. I have noticed during this last month that when I log on, some but not all of my most recent finds get included immediately. The missing ones eventually show up from the systematic update process after a few days.

CopperWings wrote:There seems to be an update problem again. I have noticed during this last month that when I log on, some but not all of my most recent finds get included immediately. The missing ones eventually show up from the systematic update process after a few days.

Everything appears to be working okay with this. One thing to note is that when the nightly statistics are run, no updates are made. So if you log on around 4am eastern time this may occur. If not, then log out and log back in and see if that helps.

Not a big deal, but since October or so when things ground to a halt for a while, it takes overnight for my finds to show up. This has been consistent for me - I log on the site after finding a cache, then come back the next day and it is there.
Thanks for making caching more fun!

ktTris wrote:Not a big deal, but since October or so when things ground to a halt for a while, it takes overnight for my finds to show up. This has been consistent for me - I log on the site after finding a cache, then come back the next day and it is there.
Thanks for making caching more fun!

Do you know if this is still occurring? I just ran across a post from Dec. 6 in the Live API developers forum that might be the cause of this. There was no mention of Groundspeak correcting the problem or even acknowledging it so I don't know if this is the issue or not. Perhaps I should go find a cache or two and see myself.

ktTris wrote:Not a big deal, but since October or so when things ground to a halt for a while, it takes overnight for my finds to show up. This has been consistent for me - I log on the site after finding a cache, then come back the next day and it is there.
Thanks for making caching more fun!

I believe this is now resolved, see the release notes for more details.

Corfman Clan wrote:Earlier today, I made changes to include Idaho in LonelyCache. Before I turned Idaho on, LonelyCache had 174,889 geocaches, 19,112,694 finds, and 355,320 geocachers. That's not much of a change since the last report, but I wanted to snapshot the counts before any Idaho caches are added.

Not sure why, but it took awhile for all the Idaho caches to be added, but they finally finished last Thursday, 19 January. So now, with all of Idaho included, LonelyCache has 196,016 geocaches, 20,669,428 finds, and 380,068 geocachers. I have made several performance improvements to the site the last few weeks and things are running better than ever, even with the increases of adding Montana and Idaho.