Understanding the MailPoet System Status Page

The System Status page is MailPoet’s built-in diagnostic tool. It shows the health of your email sending setup, including your task scheduler, cron status, sending queue, and database integrity — all in one place.

To access it, go to MailPoet > Help > System Status in your WordPress dashboard.

Note: The System Status page is available on all MailPoet plans, including the free version.

This page is useful when:

Emails are not sending or appear stuck
Post notifications or automations are not triggering
You need to provide diagnostic information to the support team
You want to identify and fix database issues

Introduction Banner

At the top of the page, you will see a brief message explaining the purpose of the System Status page. The wording changes depending on whether you are using the MailPoet Sending Service or another sending method.

If you are using the MailPoet Sending Service, the message explains that MailPoet checks both the task scheduler (cron) and the Sending Service connection. If you are using a different sending method, it only references the task scheduler.

Task Scheduler Connection

The Task Scheduler section checks whether MailPoet can reach its cron endpoint. This is the URL that triggers the processing of your email sending tasks in the background.

You will see the cron URL displayed as a link, along with a status message:

Connection successful — MailPoet can reach the cron URL and trigger email tasks normally. You will see a green success notice.
Connection unsuccessful — MailPoet cannot reach the cron URL. Sending will not work until the issue is resolved. A red error notice will appear, along with the response that was returned, which may help identify the cause.

What to do if the connection is unsuccessful:

Click the cron URL displayed on the page. It will open in a new tab. The expected response is simply the word pong. If you see anything else — such as your site’s homepage, a login page, or an error message — something on your server is blocking MailPoet’s background process.

Common causes and solutions are covered in Sending Does Not Work (Troubleshooting).

MailPoet Sending Service Connection

This section checks whether your site can connect to the MailPoet Sending Service.

The message displayed depends on whether the Sending Service is enabled as your active sending method:

If the Sending Service is enabled: You will see either “Connection successful” (green notice) or “Connection unsuccessful” (red error notice). A failed connection could be caused by a firewall, hosting restriction, or key activation issue.
If the Sending Service is not enabled: The section shows whether a connection could be established, even though it is not actively in use. This is useful if you plan to switch to the Sending Service in the future.

For key validation errors, see Known Errors When Validating a MailPoet Key.

Cron Status

This section provides detailed information about the background cron process that powers MailPoet’s sending.

Field	Description
Accessible	Whether the cron endpoint is reachable (Yes or No).
Status	Current state of the cron: Running (actively processing), Waiting (idle until the next trigger), or Unknown.
Last Updated	The last time the cron status was refreshed.
Last Run Started	When the most recent cron run began.
Last Run Completed	When the most recent cron run finished.
Last Seen Error	The most recent error message encountered during a cron run, including the specific worker name and error details (if any).
Last Seen Error Date	When the last error occurred.

Tip: If Last Run Started has a recent timestamp but Last Run Completed shows “Unknown,” the cron may be crashing or timing out before it finishes. If both fields show “Unknown,” the cron is not running at all. The Last Seen Error field can reveal specific problems — for example, “Sending frequency limit has been reached” indicates the sending queue is processing more than your configured limit allows.

Action Scheduler Status

MailPoet uses the WordPress Action Scheduler to process sending tasks. This section shows whether it is functioning properly.

Field	Description
Version	The installed version of the Action Scheduler.
Storage	The storage method in use (typically the database).
Latest Action Scheduler Trigger	The last time an Action Scheduler task was triggered.
Latest Completed Trigger	The last time a trigger ran to completion.
Latest Completed Run	The last time the scheduler finished processing a batch.

Tip: All three timestamps should be recent — within the last few minutes to hours, depending on your sending schedule. If these timestamps are old or missing, the Action Scheduler may not be firing correctly. This could be caused by a disabled or broken WordPress cron. Learn more about the Newsletter Task Scheduler.

Sending Queue

The Sending Queue section shows the current status of MailPoet’s email sending process and lists individual sending tasks.

Queue Summary

Field	Description
Status	Whether the sending queue is currently Running or Paused.
Started At	When the current sending session began.
Sent Emails	Number of emails sent in the current session.
Retry Attempt	If there has been a sending failure, this shows which retry attempt the system is on.
Retry At	When the next retry is scheduled.
Error	Any error message from the sending process.
Total Completed Tasks	Count of tasks that have finished sending.
Total Running Tasks	Count of tasks currently being processed.
Total Paused Tasks	Count of tasks that are paused.
Total Cancelled Tasks	Count of tasks that have been cancelled.
Total Scheduled Tasks	Count of tasks waiting to be sent at a future time.

Task Lists

Below the summary, you will find up to 20 tasks listed for each status group. Each task shows:

ID — The internal task identifier, useful for advanced troubleshooting.
Newsletter — A link to preview the email associated with this task.
Subscriber — The subscriber’s email address (for emails sent to individual subscribers, such as welcome emails) or “Multiple subscribers” (for emails sent to a list).
Priority — The processing priority of the task.
Date — The relevant timestamp (scheduled date, cancelled date, or last updated date, depending on the group).

The tasks are grouped by status:

Scheduled Tasks — Emails waiting to be sent at a future date and time.
Cancelled Tasks — Tasks that have been manually cancelled.
Running Tasks — Tasks currently being processed.
Paused Tasks — Tasks that have been paused, for example due to sending service issues.
Completed Tasks — Tasks that have finished sending.

Cancelling and Rescheduling Tasks

You can cancel any sending task that is in the Scheduled or Running state. You can also reschedule any task that has been cancelled.

How to cancel a task

Find the task you want to stop in the Scheduled Tasks or Running Tasks list.
Click the Cancel task button next to it.
A confirmation dialog will appear showing the task ID and email subject.
Click Yes, cancel task to confirm.

Once cancelled, the email will not be sent, and the task will move to the Cancelled Tasks list.

This is useful when:

A sending task is stuck and not progressing.
You scheduled an email by mistake and need to stop it before it sends.
A running task appears to be stuck and is blocking other emails.

How to reschedule a cancelled task

Find the task in the Cancelled Tasks list.
Click the Reschedule task button next to it.
A confirmation dialog will explain what will happen:
- If the original scheduled date has already passed, the email will be sent immediately.
- If the original scheduled date is still in the future, the task will be rescheduled for that original date.
Click Yes, reschedule task to confirm.

Note: If the task’s status changes before you confirm (for example, if the system processes it in the meantime), you will see an error message. Refresh the page and try again.

Data Inconsistencies

The Data Inconsistencies section only appears if MailPoet detects orphaned or invalid records in your database. Under normal circumstances, this section is not visible, which means your data is clean.

Data inconsistencies can be caused by:

Manual changes to the database
Plugin bugs or unexpected PHP crashes
Execution timeouts during sending
Database migration issues

When inconsistencies are detected, a table appears listing the type, the number of affected records, and a Fix button.

Inconsistency	What It Means
Orphaned Sending Tasks	Sending tasks that exist without a corresponding queue entry. These leftover tasks will never complete.
Orphaned Sending Task Subscribers	Task-subscriber records where the parent task has been deleted.
Sending Queues without Newsletter	Queue entries where the associated email has been deleted. These can block the queue from processing new emails.
Orphaned Subscriptions	List membership records where either the list or the subscriber no longer exists.
Orphaned Links	Email tracking link records where the associated email or queue no longer exists.
Orphaned Newsletter Posts	Post notification association records where the email no longer exists.

How to fix inconsistencies

Click the Fix button next to any inconsistency listed in the table.
MailPoet will permanently remove the orphaned records from your database.
A confirmation message will appear and the count will update.
If all inconsistencies are resolved, the section will disappear.

Tip: Fixing one type of inconsistency may sometimes reveal a different one. For example, removing orphaned queues may surface orphaned task subscribers. If new inconsistencies appear after clicking Fix, simply click Fix again for the new items.

Sharing System Status with Support

When contacting MailPoet support about sending or triggering issues, include the following to help the team diagnose your issue faster:

A screenshot (or multiple screenshots) of the full MailPoet > Help > System Status page.
A copy of the text from the MailPoet > Help > System Info tab. Click inside the text area and copy all the content.