[not a bug] 5.2.13 upgrade no cron job email sent.

[And then there was one les]

Updated yesterday and my cron email has since stopped being sent, i get the emails from the domain sync but none from the daily cron. So far as i can tell tasks are completing as i have seen invoice emails being send out but appears not the daily cron.

[Matt]

We have not had any other reports of issues with the cron in the latest update. If you continue having problems, please open a ticket.

 

Matt

[rickenbacker]

I have the same issue, since updating to 5.2.13 the cron no longer runs, I don't get email notifications and the activity log shows the cron is not running. When I run the cron manually however it works fine, any ideas?

 

Thanks

[webpoint]

Here the same issue.. it runs manually only, bit don`t see to do something. DB backups are not send to!!!

We get a strange mail loop in the support department. Before the update everything was ok, now when a customer is answering a ticket per mail, the system opens 20 new tickets with subject "#619156 - Support Ticket Not Opened".

 

Total mess here... Please fix the issues ASAP.

[And then there was one les]

Hello, i dont know the reason for this happening, on the day of installation the cron job did not run, but it has done since.

[wsa]

I got a email everyday from cron job

[webpoint]

Hello, i dont know the reason for this happening, on the day of installation the cron job did not run, but it has done since.

 

Maybe you are right, cron job is sending now the backup.

[And then there was one les]

I dont know what happened it was just an odd one time deal that resolved itself, i thought maybe it would show in the cron logs but it wont because for all intent and purposes the daily cron did run i just didnt get the email. Everything else it appears ran according to plan, invoices were created and according to the system emails were send out, i have not actually checked any mail logs to see what actually sent out on that cron run. it seems somewhat pointless now though with the job doing as its told

 

Anyway its not a system bug, maybe just a quirky little thing that was a little confusing.