On Dec 18, 10:36 pm, Mark McGranaghan <[email protected]> wrote: > We recently found an error in our system that was causing cron logs to > become inaccessible some time after the cron job ran, and have > deployed a fix for it. Any cron jobs running from now forward should > have cron logs accessible as expected. Also, all recent cron jobs > should have run as scheduled even if you were not able to access their > logs. > > Note that if you are using the new beta logging addon (http:// > addons.heroku.com/logging), all application logs including cron logs > are retrieved with `heroku logs`. If you are not using this addon, > `heroku cron:logs` should not be affected.
That should read `heroku logs:cron`. > We are sorry about the trouble; please let us know if you do not start > to see your cron logs or if you otherwise have problems with cron > logging. > > - Mark > > On Dec 14, 2:45 am, themire <[email protected]> wrote: > > > > > > > > > I have an outstanding ticket with Heroku support on this. They've > > suggested to upgrade to the new logging which I've done but hasn't > > done anything, they also suggested to use "puts" for output which I > > had anyway. Will let you know if they sort it out. -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
