What is the Newsletter Task Scheduler?

MailPoet sends emails in batches and not all of them immediately. They are added to a sending queue and the newsletter task scheduler is responsible for making sure that all the batches of emails in the queue get sent one after the other.

To work properly, the newsletter task scheduler needs to be triggered by an event to run continuously. You can access it by going to the MailPoet > Settings > Advanced tab.

Configuring the newsletter task scheduler

We offer two options for you to select:

1. Visitors to your website (default) 

Every visit (page load) to your website starts the task scheduler that temporarily runs in the background until all emails are processed. 

It's mostly recommended if:

  • your hosting provider restricts daily/weekly CPU usage;
  • you don't schedule your emails and send them upon creation.

2. Server side cron (Linux cron) 

A server-side script that runs frequently to trigger any task of your choice. You can read how to set it up here.

Mostly recommended if:

  • your website does not receive much traffic (e.g., 10 or fewer visitors per hour) and you need your emails to be sent exactly when scheduled;
  • you have issues with high CPU usage on your server;
  • you have any other form of sending issues (e.g., your site is behind a firewall).

MailPoet's own script 

This is no longer available for 3.89.0 version or higher.
This used to be an option for versions older than 3.89.0. If you're using an updated version of the MailPoet plugin, the MailPoet's own script is no longer available in the plugin's settings. If you had this option selected, once you update the plugin it will be automatically switched to the "Visitors to your website" option.

The task scheduler runs as a non-stop background process and does not depend on site visitors or require an external source to start. While this method is very accurate and fast, it uses minimal server resources on a constant basis and may not be compatible with certain hosting providers (the list is not exhaustive) that place restrictions on running background processes.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.