Just added issue 3020: http://code.google.com/p/googleappengine/issues/detail?id=3020
On Mar 26, 8:15 am, jeffroloff <[email protected]> wrote: > I've seen the same problem. It appears that the parsing error aborts > the cron update, so the existing cron jobs are left in place when > viewed from the AppEngine dashboard for my app. Here is the first > entry in my cron.yaml file (the one that causes the failure): > > cron: > - url: /email/Sales0/start > schedule: every monday 07:15 > timezone: America/Chicago > > I really need to change a run time for this weekend, so I'll log this > bug in a few minutes. > > Jeff > > On Mar 26, 4:12 am, morten <[email protected]> wrote: > > > Hi, > > > We have a single cron job in our cron.yaml: > > > cron: > > - description: Daily statistics job > > url: /admin/stats?action=runDailyStats > > schedule: every day 06:00 # UTC > > > When we try to deploy this after the 1.3.2 update it fails with: > > > Error parsing yaml file: > > Unable to assign value 'every day 06:00' to attribute 'schedule': > > object.__init__() takes no parameters > > in "/Users/morten/Development/agon-gae/cron.yaml", line 4, column 13 > > > I don't see anything in the release notes regarding the cron feature, > > so I hope somebody can tell us what we need to do to make this cron > > job work again. > > > Best regards, > > Morten > > -- 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.
