On Tue, Jun 25, 2013 at 1:45 AM, julien boucher <[email protected]> wrote: > I deployed an app with a set of periodic tasks a week ago. > Everything went fine for a week - using heroku free instance as a worker > dyno (no web server active). > > Yesterday afternoon, I started the web server for 10 minutes and shut it > down in the Heroku interface. > Since then it seems the worker is idling and it is not sending any periodic > task anymore.
Well, if the worker is idle then it's not alive enough check the system clock to start processing jobs again/triggering invocations. If you have a fairly loose latency requirements and can't use all the resources of one dyno all the time, I suggest using the scheduler addon to process trigger work every ten minutes or so: https://addons.heroku.com/scheduler This way, if there's no work to do the job will just exit more or less right away, incurring the billing of a trivial number of dyno-hours/seconds. -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
