Thanks for the reports, we're looking into it. In general, if there's an app engine issue that causes cron to miss a job, it will be executed once the system recovers, i.e. jobs are not entirely dropped. The exact time the task will execute depends on the frequency and scheduling. If you're seeing an issue where a task was completely dropped and never executed, please provide details about your app id and what you're seeing. Thanks.
On Oct 24, 11:53 pm, Chris Prinos <[email protected]> wrote: > Ok thanks for confirming you saw this as well. > > Looks like the same thing occured today, same time frame as before. > > Chris > > On Oct 22, 11:02 pm, sodso <[email protected]> wrote: > > > > > Yes, same happened for me as well, looks like CRON jobs arent > > reliable, so i have decided to implement double-checking logic to > > check whether the job has run or not by using a datatstore / memcache > > record > > > On Oct 22, 7:51 pm, Chris Prinos <[email protected]> wrote: > > > > Anyone know if there was scheduled down time 10/22/2010 around 12:30AM > > > PDT? > > > > None of my cron-initiated requests were triggered from about 12:33 AM > > > PDT to 1:05 AM PDT, but there were no errors in the logs. -- 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.
