|
edwardkay
|
November 1, 2024 at 9:03 am
Hi,
EE has been working really well for a couple of years now. Emails have been generated and sent as expected.
This morning, I manually triggered a set of batch emails to certain attendees of an upcoming event. I noticed that 2hrs after scheduling these, they were stuck in ‘Queued for generation’. I manually triggered the generation and they sent successfully.
I have now noticed that none of our emails are being generated; they’re all stuck in ‘Queued for generation’.
I have ssh access so ran wp cron event list. There are a number of AHEE hooks listed, but comparing with the image on https://eventespresso.com/wiki/wp-cron-and-event-espresso/, I see AHEE__EE_Messages_Scheduler__generation is missing. (I’ll add a private message with a screenshot).
I have tried switching the “Generate and send all messages” setting from separate request to same request, and back again, but this the generation cron hook is still missing.
What could cause this cron hook to be removed?
How do I add it back?
Thanks
|
|
edwardkay
|
November 1, 2024 at 9:05 am
This reply has been marked as private.
|
|
Tony
|
November 1, 2024 at 9:18 am
Hi there,
Cron jobs can fail to be rescheduled if there is an error/timeout on the request to run and reschedule them, it’s rare but can happen.
We added a check within the AHEE__EE_Messages_Scheduler__cleanup cron to confirm the other crons were still active so the first thing I would do here is run that task and see if AHEE__EE_Messages_Scheduler__generation is re-added after that runs.
|
|
edwardkay
|
November 1, 2024 at 9:29 am
Perfect!
I ran AHEE__EE_Messages_Scheduler__cleanup and now the AHEE__EE_Messages_Scheduler__generation task is back.
Thanks again for your support Tony. Really appreciate it.
|
|
Tony
|
November 1, 2024 at 10:14 am
Great, I’m glad that worked!
So if it happens again, the cleanup job should re-add either of the 2 AHEE__EE_Messages_Scheduler__* crons and __cleanup runs once_daily so it would normally fix itself within a 24 hour period (and whilst I’m not saying that’s ideal, it means messages will usually start sending again within that timeframe).
If you do notice that it keeps happening we can try adding some debug logging to the function called by that cron to see if anything shows up from that.
|
