fo2gra4

I guess they fixed it today, but those of us that had our PQ's to run on Friday will lose those and we will have to run our PQ's on Saturday and hope there are no changes between this morning and tonight for our Sunday Caching Run. Also lost time out of caching today, due to the fact we now have to run a PQ today instead of last night.

I am also having Pocket Query issues. Tried to run a previous set that was last run 10/31/11 and they never ran, than I set up a new set of Pocket Queries and marked them to run today. Well that was about an hour ago and still no pocket query has run. This is starting to be a pain. I like running my Pocket Queries on Friday to get up to date caches to go find over the weekend, but I guess that will not happen. So I guess I have to us my old info and possibly have to go after caches that have been temporarily disabled since my last PQ ran. That is a big bummer, what is going on Groundspeak?????

Check out this link to the many posts of others that have had this issue. PQ Issues So you are not alone in this! A lot of us are experiencing this problem.

I too had this issue on Saturday evening. Ran the usual five PQ's that I have used for a few months, but when I went to download them they disappeared as I clicked on each one. I remember that this happened awhile back ago, so Sunday morning I made 5 new PQ's and they worked fine. I notice that there were quite a few new caches published today, so I ran the 'new' PQ's again today (Monday) and they said that they were ready to be downloaded. Yet once again when I tried to download the files, they just disappeared. Needless to say I can not run my another 5 PQ's until tomorrow (Tuesday). Do we need to make new PQ's each time we want to update our PQ's database to load to our GPSr? Groundspeak, what is going on? Please let us know, otherwise I guess I will just have to run new PQ's each and everytime. I know you probably do not want that. Please advise all of us what is going on and when it will be fixed. I don't want a refund, just that our PQ's will run properly. Thanks in advance for your attention to this matter.

I have to agree. The current size list is working just fine. If you want to make it easier to find a cache by changing the size you may want to rethink about geocaching. Some of us like the challenge!

That is the best way of getting all the caches without overlapping. That is the way I do my PQ's, I agree with Corey and suggest you try your PQ's by Date Placed as suggested.

That is the best way of getting all the caches without overlapping. That is the way I do my PQ's, I agree with Corey and suggest you try your PQ's by Date Placed as suggested.

The way you are talking it sounds like you are the server administrator for Groundspeak. So is this a "Official Response" in dealing with the PQ issue. And if this is an "Official Response" can you say for sure that the deleting and resubmitting of PQ's is what caused this issue??? If this is an "Official Response" why is it not addressed that way? I also notice that you do not have "Groundspeak Lackey" or anything else stating you work for Groundspeak. The only thing I notice is that you are a "Premium Member". If this is not an "Official Response" from Groundspeak, please retrack your statement about being an Administator on the Server. Most of us are still waiting for an "Official Response" from Groundspeak! Not just some other geocachers opinion.

Ok, this forum string concerning "Pocket Queries" not running properly started almost a week ago (6 days to be exact). While there has been complaints, concerns, etc. There has been no further response from Groundspeak since Raine's reply on October 10th telling us that the PQ's will run, and that the PQ Generator was running at full steam. Well we are still waiting for answers to many questions, response to how things are suppose to run, etc. from someone at Groundspeak. Can we get an Official Response please. I would like to know if I have to submit a "New Request" for PQ's each time I need a PQ, or will the PQ Generator start working properly again? And when will it start working properly? I would like to know this information since I have lost out on the ability of submitting some PQ's when the day before PQ's showed up late (the next day after they were submitted, almost 15 hours later), and the PQ Generator tells me that I am over my limit of 5 when I only submitted one PQ for that day. Please, please, help!!!!!

Don't think I would agree with you about the TB issue and marking a cache as "Needs Archived" just because he/she does not verify the TB situation. If the person who looked for the TB told the owner of said TB, then that TB owner is responsible for marking it as "Missing". (Yes I know the cache owner can do the same) I have had a few cachers in the past say that a TB logged into my cache was not there, then a few weeks later I have a chance to check on the cache and surprise - guess what is in the cache. I have also had someone say that the TB was not in the cache and a few weeks later a cacher who visited the cache (after the one who said it was missing) logged the trackable out of the cache. So how does your theory of marking the cache said trackable was in as "Needs Maintance" or "Needs Archived" help find the supposive missing trackable? And by your theory, how do you arrive at the conclusion that the owner is not maintaining the cache? Like I said, it may just be that someone did not look or took the time to look throughly!

Ok, New PQ's are working fine without any problems. That's great! But...... When will the "scheduled" PQ's (or those run in the past) be fixed not to take almost half a day or so to run? If you submit a PQ on one day it should run on that day - not run on the next, and if it does it should not take away from the nexts day PQ limit. Any word yet Groundspeak???? Do you want everyone to run "New" PQ's from now on and not run the ones they already have ran in the past????? Please let us know your position!!!

Sitting here thinking about the issue. If it is indeed because of the PQ Generator being slow, then can we get our limit increased to 10 PQ's per day instead of five? Wait then that will slow things down even more. Please let us know how you plan to fix these issues with PQ's not running properly Groundspeak. Please!!!!!!!!

Ok, I still don't understand why there is a problem but there is. Like I have asked before, when running your PQ's on one day but receive it on the next day. Why do you lose out on your PQ's? I ran my PQ's that I usually do on Sunday at 9:30pm EST, but did not receive them until Monday at 2:30pm EST. Needless to say when I tried to run my PQ's on Monday I was told that I exceeded my limit of 5 PQ's. My question like it was earlier in this string and is like above the above question is: Why do we lose the current days PQ's, when the day before PQ's show up late????????????? This is not the fault of your paying Premium Members, and Groundspeak is the one that puts the limit of 5 per day! Groundspeak, please respond to your paying Premium Members questions on this forum string!

Thanks for the reply! I never knew there was an order of priority for the PQ's, not sure if others knew it either. Your reply may help others if they are trying to get an update of their PQ's before going on vacation. What is the "Official Word" on the PQ Generator? Is everything working fine now?

As stated by Corey, only the Owner of the Missing TB/GeoCoin and the Owner of the Cache that the item was in has the ability to mark the trackable missing. As a finder of the cache, you can click on the "Missing" trackable from the cache page which will bring you to the "TB/GeoCoin Page" and you can then log a "Write Note" and say in that note that you believe the item is missing. This way the owner knows what is going on with his/her TB/GeoCoin and then mark the item missing if they so choose. It would also be nice to mention that the TB/GeoCoin is missing when you log your find of the cache. This way others who find the cache in the future know it has not been seen there, and then the Owner of the Cache can mark it missing if they so choose. I hope this helps.

New Query's take priority, so they will instantly hop to the top of the list to run when submitted. If you have a PQ that you want and it's been a while and it still hasn't ran, then go to your list of PQ's. Look for copy PQ. Make a copy of the PQ you want and then that will pop up on your list of PQ's. Hit today's date and you'll have that PQ sent to you very quickly. This works about 98% of the time. This make the copy of the PQ you want and since it's never been ran or submitted before it will hop to the top of the list. I had one the other day that just wouldn't go and I set it for that day the day before. I finally was getting down to time to leave and still didn't have my PQ. So I did this and had the PQ in less than a minute. I don't know if people realize, but until they delete the toxic pocket queries that are failing to run and insert completely new ones they will continue to have the problem. There is something in the range of queries created between Wednesday afternoon and Saturday morning that causes them to NEVER be queued in the query processor. This is what the evidence says so far, and we won't know differently until Groundspeak gives us an explaination. Nudecacher It is nice to hear that this works for some of the cachers out there, but from the posts I have read it seems that it does not work for all of them. Also where did you get the info that the "New" PQ's go to the top of the list? I was under the impression that the PQ's ran as they were submitted, or in the case of the scheduled ones that they would run just after midnight on the date it is scheduled. Once again, it would be nice to hear some Official response from Groundspeak on this Issue. Also now that the issue of how PQ's run has been brought up, it would be nice to have that clarified also.

Prior posts from Groundspeak lackeys in this thread demonstrate otherwise. If it makes you feel any better, I'm leaving now for a three-day roadtrip and I'm missing two scheduled queries from Friday, as well as the copies I created to run today. Yes there were two posts from Raine, but one was asking if it was Regular PQ's or Route PQ's. The other one was saying that they were aware of the problem and that the PQ generator was running at full steam, and not to worry you will get your PQ's. If they are the posts you are talking about, how does that help or answer the many Premium Members questions. To me those posts where not a response about the issue!!!!! And I am still having problems with PQ's, so the problem is not fixed in my opinion. And I am still hearing the same from others, as well as hearing some are now getting their PQ's. Now how about it Groundspeak? What is going on? Recap of prior questions that have not been answered. Groundspeak, at what time and date will this issue be fixed? How long should we have to wait for a PQ after we submit it? If we submit the PQ on a lets say Thursday but we do not get it until after Friday (PST), why do we lose a PQ for Friday since the request went out on Thurday? And yes Motorcycle Mama, I agree that Raine did answer that he was aware of the problem. There just has not been any reply or post to what is being done to fix the problem, when will the problem be fixed, etc. It is fine that he acknowledged the problem, but there should be more coming from Groundspeak on this issue. Especially since we pay for this feature.

This problem with PQ's have been going on for quite awhile for me. I would submit a prior and/or new PQ and it would take some an hour or so, then others 8 hours or so. As I have said this is nothing new for me, it has been going on for a couple of months. Just got around to see if anyone on the forums are having the same issue. Now I see there has been. I would not blame it on the GeoCoin Fest, since this issue started well before then. My question is: When will this issue be fixed? It has been fustrating submitting a PQ and not getting it before it is needed. Up until a couple of months ago I had no problem when I submitted a PQ, it came within a few minutes. Why not now? Groundspeak, at what time and date will this issue be fixed? How long should we have to wait for a PQ after we submit it? If we submit the PQ on a lets say Thursday but we do not get it until after Friday (PST), why do we lose a PQ for Friday since the request went out on Thurday? From the looks of this forum string, inquiring minds want to know!!!!!!!!!!!!! Please give us more information on what is happening, not just that the PQ Generator is cranking them out!

Ordered the whole set! Very nice work StressMaster! Can't wait to get my hands on them!!!!!

Emailed ChileheadCraig about two of his caches, and I think that Dark Onyx email him about the other four. I hope this helps.

hmmmm, or possibly one these to recover those caches in potentially life threatening situations, at least I could say I took most reasonable precautions should I be injured and tempted to litigate: I want one of both!!!!

I also have a GeoBackPack (a converted BookBag). In this one I carry: Maps, Local Brochures, Paper, Flashlights, Gloves, HandiWipes, Pens, Logs, and whatever else I would need (from my GeoBox) to take with me on a hike to a cache.

Ok, let's see. I have a GeoBox (a converted tool box). All my trade items (TBs, Geocoins, GeoJunk), various sizes of ziplock bags, batteries, knifes, various micro hides, camo tape, zip ties, velcro, pens, tweezers, scissors, dental pick, hemostat clamp, mirror on a stick, compass, stapler with staples, rain poncho, fire tacs, magnets, glow stick, flashlight, super glue, gorrilla glue, geobusiness cards, and cache logs.

Thanks for this information, I now have my "notifications" set up to let me know about any Cache in my area that is Archived. Just the info I needed, thank you very much. I knew I would get the info I needed here!

Mushtang, sorry if you thought my whole post was talking about you. I used your post to show the change to venomous snake from poisonous snake. Then I went about posting to the rest of the topic on responsibilities. Sorry if I offended you. My apologies!