Mailpoet Cron – Why every 2 minutes?

Hi there,

Thanks for reaching out!

Why mailpoet/cron/daemon-trigger needs to run every 2 minutes (standard)? Can I change to a longer time and what would happens

I confirmed with our developers that it’s expected that this task run every two minutes.

Is this causing any issues on your site?

I appreciate it if you could respond directly to my question rather than posing another question. This is what support is for, isn’t it? I’m unsure why it needs to be run 720 times a day; that seems excessively high.

• This reply was modified 1 year ago by vivobook.

I’m unsure why it needs to be run 720 times a day; that seems excessively high.

The trigger action (?mailpoet/cron/daemon-trigger) that every time the Action Scheduler runs, it checks whether there are jobs to process since MailPoet sends emails in batches, and not all of them immediately.?

Unless there are jobs to process, it does not do anything except schedule again two minutes later. You can read more about this here Newsletter Task Scheduler (cron) – Documentation.

That said, we’re interested in knowing more about your issues or concerns about the scheduled action. If that requires changing something on the plugin end, we can promptly share that with the developers for further investigation.

Thank you for your understanding.

Thanks again.

I do understand, but can you tell me a job which needs to be triggered every 2 or 5 minutes? I can’t think of such a job in mailpoet.

Can you ask your developers? I still think every 2 minutes, 720 times a day, is excessive and unnecessary.

Over and out…

Hi @vivobook,

My understanding is that the Mailpoet jobs are being triggered by the action scheduler events. But I will check with our developers and keep you posted.

Why are they being scheduled when there are no newsletters to go out?

We had 15k+ cron entries in the db that are useless and no newsletters/emails were scheduled to dispatch. It’s a waste of resources for that to happen, especially for sites with low resources. Can’t this be stopped unless we decide that a newsletter should go out. The logging is not needed every 2 minutes unless there’s an error, then _maybe log once a day.

B C. a11n?(@battouly)

3 months, 3 weeks agoHi?@vivobook,

My understanding is that the Mailpoet jobs are being triggered by the action scheduler events. But I will check with our developers and keep you posted.

__________________

Keep you posted? It’s almost 4 months ago! Don’t post you will do this or that, rather take actions and then post the facts. Thanks.

Hello again @vivobook,

Thank you for reaching out to us.

Why does MailPoet need cron to run every 2 minutes?

MailPoet’s default setting to trigger cron jobs every 2 minutes is designed to ensure timely delivery of emails, smooth automation workflows (like welcome emails and automatic post notifications), and accurate subscriber management tasks. Tasks such as processing bounces and tracking opens/clicks are vital for maintaining the health of your email lists and ensuring the delivery of your newsletters.

Can I change the frequency of the cron jobs?

Yes, you can adjust the frequency of the cron jobs. However, its essential to understand the potential implications. Increasing the interval between cron tasks may delay email delivery and slow down the real-time processing of subscription confirmations, automated emails, stats updates, and other crucial time-sensitive operations.

Setting Up a Custom Server-Side Cron Job:

For those with concerns about resource usage or those who want more control over their website’s performance, configuring a server-side cron job (Linux Cron) is a robust solution. This allows you to specify the frequency that best suits your website’s needs and resources.

Please refer to our step-by-step guide on setting this up: Setting the Server-Side Cron (Linux Cron).

This guide will walk you through how to replace the MailPoet’s default WP-Cron with a real cron job directly from your server, offering you full control over its execution frequency.

Addressing Unused Cron Entries

We understand the concern regarding the accumulation of cron entries, especially when no newsletters are scheduled. Our developers continuously strive to optimize MailPoet’s performance, and we take feedback on resource usage seriously. Reducing unnecessary load is a priority, and your observations have been forwarded to our development team for further review and possible improvements in future updates.

Final Thoughts

It’s our goal at MailPoet to balance functionality with efficiency, ensuring our plugin meets your needs without compromising your site’s performance. We appreciate your feedback as it helps us make MailPoet better for all our users.

Should you require any assistance with setting up the server-side cron or have any further questions, please don’t hesitate to get back to us. We’re here to help make your experience with MailPoet as smooth and efficient as possible.