Ben H

We are aware of the bug with the caches along a route form. The engineering team has already fixed the issue and it will be released ASAP.

One of our engineers identified the problem and has kicked off a data reindexing process that should fix the strange results you were seeing within the next 20 hours or so. In the meantime, could you post here regarding the exact steps you used to log the geocaches that are showing up incorrectly? One hypothesis is that you may be using a logging method that currently isn't captured in our data indexing. We'd like to remedy that if possible. Thanks!

Thanks for reporting your issue. I was able to reproduce it as described on your account. We will investigate the problem.

Yes, we're still investigating options for delivering search results to standalone GPS devices.

Thanks for the reports on this issue. It is, indeed, a bug. We'll fix it soon.

This bug should be fixed now. Please let us know if you continue to see it.

Thanks for reporting this. We will fix it ASAP.

An interesting, but 100% incorrect guess.

Thanks for the appreciation and, more importantly, for the feedback. We knew going in to this work that an option for bulk selecting search results would be very important for many players. With that in mind, bulk select has been part of our plans from the outset. We wanted to put this first chunk of new functionality on the search page into players' hands as soon as possible, but rest assured we will be following up with additional improvements including an option for bulk selection.

We are aware of the reported problems and investigating now.

The fix for this bug has now been released. You should once again be able to use the new search's GC code dropdown option to go directly to the page for a specific cache, including archived caches. Let us know if you continue to see problems. Thanks!

That is, indeed, a bug. Thanks for noticing and reporting. We will fix it as soon as possible.

Yes.

Absolutely. Each cache that receives an email is flagged in our database, thereby enabling the generation of reports about whether change is effected over time. Since the first emails were sent less than 48 hours ago, it's too soon to do that now. Please keep in mind that the >10 caches that have been discussed so far in the forums represent an exceedingly small sample of the first batch of caches that got these emails. While there is certainly good information in these discussions that might help improve the system going forward, it is not fair to judge the entire system on a handful of anecdotal cases. The success or failure of these emails will be proven by data over time.

Thanks for the suggestion, niraD. Customizing the emails to the specific cache is something we did consider as we developed this project. We are monitoring feedback already and we'll continue to keep an eye on whether adding that kind of detail might be necessary.

That's a great lead. So the errors you're seeing happen in Explorer, but not in Firefox, right? Thanks again.

Hmmm...I'm still not able to reproduce any anomalous sorting using your link or several of my own searches. Could you detail the exact steps you go through that end with the erroneous sorts? Any additional detail (including your browser, OS, etc) you can provide would be very helpful for us in diagnosing potential issues. Thanks!

Thanks for reporting the issue. I'm currently not able to reproduce the error using the URL you provided. I know you mentioned that the problem seems intermittent, but are there any other steps you can provide that cause the error you're seeing with some consistency?

Awesome! Thanks so much for checking again and reporting back.

We released an update to the search page this afternoon which fixes a bug that we believe was causing the issue you described (along with other erroneous results). Please try your initial search again and let us know if you continue to see errors in the results. Thanks for reporting your issues!

We released an update to the search page this afternoon which fixes a bug that we believe was causing the issue you described (along with other erroneous results). Please try your initial search again and let us know if you continue to see errors in the results. Thanks for reporting your issues!

We released an update to the search page this afternoon which fixes a bug that we believe was causing all of these issues. Hopefully the incorrect results are no longer being returned in each case. Please let us know if you continue to see errors in the search results.

This does appear to be the same bug. The search is incorrectly returning multis and mysteries that the searcher has found, owns, or has added corrected coords or a personal cache note to. We will be looking into the bug tomorrow.

Thanks for reporting your issues. We have been able to reproduce some searches with incorrect result sets. It appears that one of our recent updates introduced a bug regarding multi and mystery caches in the search results. We are working to fix it ASAP.

Thank you for reporting the issue. I am able to reproduce the error, so I have added a bug to our system. We'll get it fixed ASAP.