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 Settings → Advanced tab.

Configuring the newsletter task scheduler

We offer three 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. MailPoet's own script

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.

We suggest you select this option 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 run a high traffic web site (e.g., 10+ visitors per minute, which may include crawlers/bots), because option "Visitors to your website" may result in excessive database queries that could put a strain on the server.

3. 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:

  • 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).
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.