We had a nightly job on our development server to which we also did a
daily automated build.

The cron job never executed. It took me forever to understand why.

I'm not sure why it is designed this way.

j

On Nov 18, 3:12 am, djidjadji <djidja...@gmail.com> wrote:
> I have a simple cron job that needs to run "every X hours"
>
> --------------- cron.yaml -----------------------
> cron:
> - description: Hourly Check
>   url: /jobs/check
>   schedule: every 1 hours
> ------------------------------------------------------
>
> If I upload a new version of the app the schedule time of the cron job
> is reset. I haven't changed cron.yaml.
> The dashboard cron jobs page shows "hasn't run yet" after an upload.
>
> Why is the schedule time reset on upload of application when the cron
> job is not changed?
>
> Why is the cron job not scheduled/called immediately (or 1 minute)
> after the upload, if the reset is needed?
> Then the job would be called a few times to much but at least it gets called.
>
> If you have an "every 3 hours" and you do a few uploads in a day the
> cron job is hardly ever called.

--

You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=.


Reply via email to