Jump to content

PQ problem


Bus&Betty

Recommended Posts

Posted

Yesterday, I created a new query and my PQ triggered without problems.

 

Today, PQs will not trigger for my newly created queries. I tested an old query, last ran in August, and it triggered just fine.

 

Thanks,

Patty (aka B&:drama:

Posted

I'm not sure why this occurred, but I reset your two queries scheduled for today. Please reply if this continues.

 

What great service :drama: The reset did the trick.

 

Thanks

Posted

I'm having troubles today, too.

Set up a couple of new PQs near my new home location and they don't want to run.

They return caches on the preview but they aren't going out to the email and the run date says 'never'.

I noticed when I did the queries (these were new ones) it just said the query had been saved, which it was. But it doesn't send anything to my email.

Posted (edited)

I'm having troubles today, too.

Set up a couple of new PQs near my new home location and they don't want to run.

They return caches on the preview but they aren't going out to the email and the run date says 'never'.

I noticed when I did the queries (these were new ones) it just said the query had been saved, which it was. But it doesn't send anything to my email.

Same problem here. I ran PQ for user routes and they are fine. Try to run regular PQs, from a known geocache, and i have the same problem.

Edited by Famgeo
Posted

I'm having troubles today, too.

Set up a couple of new PQs near my new home location and they don't want to run.

They return caches on the preview but they aren't going out to the email and the run date says 'never'.

I noticed when I did the queries (these were new ones) it just said the query had been saved, which it was. But it doesn't send anything to my email.

DITTO!

Posted (edited)

I created a PQ today several hours ago and it was not processed yet.

 

I tried deleting it and creating a new one but that didn't help but a "my finds"-query that I ordered at the same time was sent to me.

 

Update:

I just noticed there must have been an error in the filter criteria so I had to rebuild the query.

Maybe the PQ server just wanted to save me from getting a PQ with just 5 caches?

Let's see how long it takes until the new one gets processed.

Edited by Starglider
Posted (edited)

We're looking into this issue. Sorry folks.

 

Edit: "New" instance crashed. It's starting up again now - only 800 behind. It should catch up in about 5 minutes.

Edited by OpinioNate
Posted

Got them, thanks.

 

We're looking into this issue. Sorry folks.

 

Edit: "New" instance crashed. It's starting up again now - only 800 behind. It should catch up in about 5 minutes.

Posted

I have had zero luck with a query along a route. I have several already built and they will not run. The new one I built from Detroit to Milwaukee won't run either. A request returns nothing but errors!

 

What can I do, I am leaving on the road in 24 hours and would like to cache along the way.

Posted

I have had zero luck with a query along a route. I have several already built and they will not run. The new one I built from Detroit to Milwaukee won't run either. A request returns nothing but errors!

 

What can I do, I am leaving on the road in 24 hours and would like to cache along the way.

 

Have you had any luck? Check your spam filter if you use a free web mail account. Also make sure the last generated date is lighting up.

Posted

I started 2 PQ to run (PQ's were already created some weeks ago), about 8.30am this monday. But now, 2 hours later (10.25am) i still havent received them on email.

 

Team WECA

Posted

I submitted 4 PQ's about an hour ago. These are PQ's that I run almost every week. The last 2 I submitted ran, but the first 2 have not run yet.

 

Thanks for any help.

 

NClingen

Posted

Looks like there may be a slow-down of the PQ processor(s).

 

I have 4 standard PQs that run every Monday. 1 ran at 3:48AM. The other 3 haven't yet run, including one that last ran 9/28/2009 12:58:40 AM so it should be pretty close to the top of the queue.

Posted

Sometimes the "old PQ" processor fails but the "new PQ" processor is still running. No idea if that is what is happening here, but if you haven't already done so I'd make a new PQ and see if that runs. (I know old PQs are very delayed at the moment.)

Posted

My scheduled pocket query didn't run yesterday or today. So, add me to the list.

 

However, My Finds ran just fine last night when I requested it.

Posted

Some ran some didn't. UP6 and UP7 ran at 12:07:29 this morning, UP8 was submitted at the same time last night, it is still waiting.

 

How about a reset.

 

Thanks.

Posted

There does seem to be an issue with certain longstanding PQs suddenly failing to generate. In this next sprint we're converting the Pocket Query Generator app into a service, so when the PQs get stuck in "naughty status" (the dev's term) they won't keep timing out.

 

If you find your scheduled PQ (does not apply to *new* PQs) failing to generate, send a quick email to contact@geocaching.com and we'll reset it for you. Please wait some time after checking the day for your PQ to run to ensure that it really is failing.

Posted

The ones I'm waiting for were new. Actually, it's really only one, but I ran it a couple times again, then created a "new" one once or twice.

 

I guess I'll just go for a bike ride, rather than waste the first nice day in weeks waiting on technology!

Posted (edited)

Today, I have the same problem that I reported (and was fixed) on Sept. 30th.

 

Newly created PQs will not trigger. A previously-run PQ runs triggers immediately.

 

I ran PQs on Oct. 3rd with no problem.

 

Thanks

Edited by Bus&Betty
Posted

I submitted 3 PQs this morning. 1 ran, 2 didn't. After waiting a while, I deselected the 2 that didn't run and submitted them as new PQs. They haven't run either.

 

It's been a couple of hours.

Posted

I queued 5 PQs over 4 hours ago - one ran immediately, but the other 4 have not run

Of 5 PQs requested yesterday, 2 ran immediately, but the other 3 have still not run.

Posted

I have two long-standing pocket queries that I submitted a couple of hours ago that won't run.

 

I also have two new pocket queries (copies of the above two) that I submitted about half an hour ago that haven't run.

 

Is there ANY way for me to get this information before my next caching expedition tomorrow?

 

--Larry

Posted

Similar story here. I checked boxed five queries that last ran a week ago at just before six AM PDT - one ran immediately, the other four are still checked.

It would be nice to at least see an acknowledgement from TPTB that there is a problem and it is being addressed.

Posted (edited)

Similar story here. I checked boxed five queries that last ran a week ago at just before six AM PDT - one ran immediately, the other four are still checked.

It would be nice to at least see an acknowledgement from TPTB that there is a problem and it is being addressed.

Scroll up to post #39

Edited by macatac1961
Posted

Similar story here. I checked boxed five queries that last ran a week ago at just before six AM PDT - one ran immediately, the other four are still checked.

It would be nice to at least see an acknowledgement from TPTB that there is a problem and it is being addressed.

Scroll up to post #39

But that is of little solace to those of us that have brand new queries in the queue since this morning.

Guest
This topic is now closed to further replies.
×
×
  • Create New...