|
ARAGATO
|
October 26, 2019 at 12:07 am
I was wondering why messages did not arrive. So I checked the message activities and saw that over a 1000 messages where correctly generated but were stuck in “queued for sending”. I then checked a couple of messages and sent them manually. Worked, indicator turned from blue to green. Now I was wondering why all messages in the queue are not being sent. I finally ended up in the cron manager and realised that one particualy cron job was missing “AHEE__EE_Messages_Scheduler__sending”. I readded it and now the messages in the queue are getting sent.
Nobody deleted that cron job. Why does it, and only this one disappears out of a sudden? How is that possible? And most importantly, how to make sure that does not happen again?
|
|
Tony
|
October 28, 2019 at 3:14 am
Hi Aragato,
We can’t tell you why that cron was missing on you site for certain but its possible the request to reschedule the events timeed out or threw an error which prevented the tasks from being set.
Have you checked the servers error logs from around the time that the messages stopped sending? Any error from EE? Memory exhausted errors etc from around that time?
The messages system schedules 2 tasks at once, like this:
// register callbacks for scheduled events (but make sure they are set only once).
if (! has_action(
'AHEE__EE_Messages_Scheduler__generation',
array('EE_Messages_Scheduler', 'batch_generation')
)) {
add_action('AHEE__EE_Messages_Scheduler__generation', array('EE_Messages_Scheduler', 'batch_generation'));
add_action('AHEE__EE_Messages_Scheduler__sending', array('EE_Messages_Scheduler', 'batch_sending'));
add_action('AHEE__EE_Messages_Scheduler__cleanup', array('EE_Messages_Scheduler', 'cleanup'));
}
What this is doing is checking id the ‘batch generation’ action was set, if not then none of them should have been set and it re-adds them. On your site, you somehow still have batch generation set, so the above doesn’t run.
Do you have a AHEE__EE_Messages_Scheduler__cleanup cron set?
|
|
ARAGATO
|
October 28, 2019 at 4:35 am
Hi Tony,
yeah, the AHEE__EE_Messages_Scheduler__cleanup is still running daily and as you said the AHEE__EE_Messages_Scheduler__generation is still there, too, preventing the missing AHEE__EE_Messages_Scheduler__sending from being reinstantiated.
I guess we will have to investigate in the logs and check if there was like a memory issue or anything else that might have caused it.
But, at least I now know for the future the important and relations between those Messages_Scheduler crons. 🙂
Thanks
|
