Yes double check everything if its a critical job like you mentioned, use the datastore for storing temp values for checking job status
2 times in the past few days, my CRON jobs didnt even run at all during 12AM - 1230AM or so timeline So dont rely on the CRON jobs, maybe you can submit a task (task queue) and check its Task-Retry header to ensure it doesnt run twice. task queue is much MORE reliable than CRON jobs here in GAE world cheers ! On Oct 25, 3:18 pm, Lior Harsat <[email protected]> wrote: > Hi, > > I have noticed today that on of my cron jobs ran twice !!! > I can see in the log the queue header : "queue_name=__cron > task_name=989235fd7268bdc3a1bde56c2063bcd4" for both requests. > further more in my cron jobs page in the admin console it states the > the cron ran successfully but 26 seconds late. > The requests I see in my log are 26 seconds apart. > my app id is farmigo-csa. > > Is this a bug? > Should my code also make sure the cron job hasn't run already ? > This cron job was for a billing cycle. You can understand the > implications :-( > > Thanx Lior -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
