Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

MailPoet Automation Not Working: Causes and How to Fix It

MailPoet Automation Not Working: Causes and How to Fix It

Short answer

First confirm the automation is active and your test subscriber meets the trigger after activation. Then check that MailPoet's task scheduler and WordPress cron are running, clear stuck scheduled actions, and make sure sending is not paused or failing in MailPoet settings.

Key takeaways

  • Draft or incomplete automations never run.
  • Triggers usually fire only for new events after activation.
  • Delays and every step depend on background tasks running.
  • Low traffic or disabled WP-Cron can stall automations.
  • Tools > Scheduled Actions shows stuck or failed steps.
  • Sent but missing emails point to deliverability, not the automation.

Why is my MailPoet automation not working?

MailPoet automations usually stall because the automation is not active, the subscriber does not meet the trigger, background tasks are not running, or sending itself is paused or failing.

A MailPoet automation has several moving parts. A trigger starts it, steps such as delays and emails follow, and background tasks run each step at the right time. If any part fails, the email never arrives.

The fix depends on where the chain breaks. This guide goes from the quickest checks to the deeper server issues.

MailPoet's own automation troubleshooting guide is worth keeping open as you work through the steps.

Is the automation actually active?

Open MailPoet > Automations and confirm the automation shows as active, not draft or deactivated; drafts never run, however correct the steps are.

It sounds obvious, but it catches many people. An automation saved while editing can stay in draft.

Check these points:

  • The status column says Active.
  • Every step is complete, with no warning icons in the editor.
  • Each email step has a saved email with a subject and content.

Also make sure MailPoet itself is up to date. The MailPoet plugin page shows the latest version and changelog, and automation fixes often arrive in updates.

If you edited the automation recently, open it again and make sure the changes were saved and the automation re-activated.

Does the subscriber meet the trigger?

Most automations only start for people who meet the trigger after the automation went live, so existing subscribers and unconfirmed subscribers are often skipped.

Triggers are strict. A someone subscribes trigger fires when a person subscribes to the chosen list, not for people already on it.

Common trigger problems:

ProblemWhy it blocks the automationWhat to do
Subscriber joined before activationTrigger only fires on new eventsTest with a new subscriber
Double opt-in not confirmedSubscriber is still unconfirmedConfirm the email, or check opt-in settings
Wrong list selectedTrigger watches a different listEdit the trigger and pick the right list
Subscriber is unsubscribed or bouncedMailPoet will not email themUse a clean test address
WooCommerce trigger needs an order statusOrder never reached that statusCheck the order status setting

Test with a fresh email address you control. Subscribe through the real form and confirm the opt-in email if your site uses double opt-in.

To find which form adds people to which list, see how to find the form ID in MailPoet.

Are delays holding the email back?

A delay step pauses the automation for the time you set, so an email after a one-day delay will not go out until that day has passed.

When you test, it is easy to forget a delay. Look at the automation's analytics or subscriber view to see where your test subscriber is waiting.

For testing, you can build a short copy of the automation with a delay of a few minutes. Once it works, return to the real delay.

Delays also depend on background tasks. If those tasks stop, a delay never ends, which leads to the next check.

Is the MailPoet task scheduler running?

MailPoet relies on scheduled background tasks; if WordPress cron is not running, automations stall at the trigger or at a delay step and nothing is sent.

MailPoet's task scheduler guide explains the options in MailPoet > Settings > Advanced. By default, tasks run when people visit your site.

That works poorly when:

  • Your site has little traffic, so tasks run rarely.
  • Your host disables WordPress cron.
  • Caching serves pages without triggering cron.
  • A security plugin blocks loopback requests to your own site.

On low-traffic sites, switch to a real server cron job. Our guide on using a real cron job walks through that change.

If cron seems broken on the whole site, not just in MailPoet, start with fixing WP-Cron not running.

The WordPress cron documentation explains why page visits drive scheduled tasks by default.

How do you check the System Status page?

Open MailPoet > Help and the System Status tab to see whether the task scheduler, cron and background actions are running and when they last ran.

MailPoet's System Status guide explains each field. Pay attention to:

  • Cron status and the last run time.
  • Action Scheduler information, which MailPoet uses for automation steps.
  • Any errors listed next to sending or background tasks.

If the last run time is hours old, background tasks are stuck. Fix cron first before changing anything in the automation.

Are there stuck scheduled actions?

Go to Tools > Scheduled Actions and filter for MailPoet actions; a long list of past-due or failed actions shows that background processing is blocked.

Automation steps run as scheduled actions through the Action Scheduler library. Each action records whether it ran, failed or is still waiting.

What the statuses mean:

  • Pending and past due: tasks are not being run, usually a cron or loopback problem.
  • Failed: open the action log to read the error.
  • Complete: that step ran, so look later in the chain.

Failed actions with PHP errors point to a conflict. Turn on debug logging and see the debug mode guide to read the full error.

Is sending paused or failing?

Even when the automation runs, emails stop if MailPoet sending is paused, a sending limit is reached, or the sending method cannot connect.

Check MailPoet > Settings > Send With. Look for:

  • A paused sending notice at the top of MailPoet screens.
  • A sending limit that has been reached for the period.
  • An invalid or expired MailPoet Sending Service key.
  • SMTP errors if you send through your own provider.

MailPoet's sending does not work article lists the main sending checks. If you use SMTP, our guide on MailPoet SMTP settings covers the connection details.

Could the email be sent but not delivered?

Yes; if MailPoet shows the email as sent but it never arrives, the problem is delivery, such as spam filtering or missing SPF and DKIM records.

Check the spam folder of your test inbox first. Then look at your sending domain's DNS records.

Messages sent from a domain without SPF, DKIM and DMARC are more likely to be filtered. Our guide to SPF, DKIM and DMARC for WordPress email explains the records to add.

Is a plugin or theme conflict involved?

A conflict can break the trigger or the background tasks, so test with other plugins disabled on a staging copy if the earlier checks do not explain the problem.

Signs of a conflict include failed scheduled actions with PHP errors, or automations that stopped right after a plugin update.

  1. Copy the site to staging.
  2. Turn off all plugins except MailPoet, and WooCommerce if your automation uses it.
  3. Switch to a default theme.
  4. Trigger the automation with a test subscriber.
  5. Turn plugins back on one at a time until it breaks.

Optimization and security plugins are the usual suspects, since they can block background requests.

What should you check after fixing it?

Run a full test with a new subscriber, confirm each step moves forward on time, and check that past-due scheduled actions are cleared.

A short final checklist:

  • The automation is active and complete.
  • A fresh test subscriber passes the trigger.
  • System Status shows recent cron runs.
  • Scheduled actions are no longer piling up.
  • The test email arrives in the inbox, not spam.

If everything checks out but the problem returns, collect the System Status report and contact MailPoet support. For setup basics, see our guide on using MailPoet in WordPress.

Frequently asked questions

Why didn't my existing subscribers get the welcome automation?

Most triggers, such as someone subscribing to a list, fire only when the event happens after the automation is active. People already on the list did not trigger it. To reach them, send a regular newsletter or add them again through a fresh event.

Does MailPoet automation need WP-Cron?

MailPoet relies on background tasks, which by default run through WordPress cron when people visit the site. On low-traffic sites or hosts that disable WP-Cron, set up a real server cron job so tasks run on time.

How do I see where a subscriber is stuck in an automation?

Open the automation in MailPoet and check its analytics or subscriber view, which shows which step each person reached. If many people sit on a delay that should have ended, background tasks are probably not running.

Why does MailPoet show emails as sent but nobody receives them?

The automation worked, but delivery failed. Check spam folders, your sending method and your domain's SPF, DKIM and DMARC records. Using a proper sending service or SMTP provider usually improves inbox placement.

Can caching plugins stop MailPoet automations?

They can. Full page caching may stop page visits from triggering WordPress cron, and some optimization or security plugins block background requests. Exclude MailPoet requests where needed, or switch to a real server cron job.

Sources

  1. Troubleshooting Automations MailPoet
  2. Newsletter Task Scheduler (cron) MailPoet
  3. Understanding the MailPoet System Status page MailPoet
  4. Sending Does Not Work MailPoet
  5. Cron WordPress Developer Resources
  6. Action Scheduler Action Scheduler

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.