eewanco

I think I solved the problem. When this happened before, I was playing around with changing my query to exclude "stealth" caches. I was doing the same thing when it broke this time. When I created a totally new query, manually copying the settings but without the attribute exclusion, and ran it, it worked like a charm. It doesn't seem to happen with one of my queries that includes an attribute.

I am having the same issue. In my case, I am using GSAK to process them, which will handle very long names, which excludes the name collision issue. I generate a query, preview it, it has 200 caches, then get the cache file, load it into a clean database, and it has only 38 caches (in fact, it says the file has 38 when it is loading). I've verified that I'm not using an old file (besides, it has a 200 limit but the query returns more than 200 matches, so it should always be 200 in size). Trying to test this with Pocket Query limits is difficult.

Getting an email when your friend logs a cache is a neat feature. However, I have a friend, a very insane one, who can do hundreds of caches a weekend. Hopefully there will be something that bundles up the notifications or otherwise limits them when this happens! Also you could have a daily limit of notifications, and a page to go to to see all the glorious details.

I've search for "pocket query attributes" and found this message. Sorry to bring back an old thread.. but, when would be the next update? Like a lot of people, I'm really looking forward for this new feature! Yes, I agree! Attributes are an awesome feature, being able to do our own sub-filtering would be great.