Mailster requires a cron job to send campaigns. Check its status under Newsletter > Settings > Cron, where you can see the last trigger time and details. If the cron hasn’t run recently, verify your cron settings and ensure the secret hash hasn’t changed.
Mailster prevents duplicate emails by creating a cron lock during campaign processing. If a lock is active, you’ll see a notification when accessing the cron URL. Locks are released automatically after processing, but may require manual release if a timeout or error occurs. Adjust email volume if you frequently encounter locks.
If your email campaign isn’t sending, check key settings: verify newsletter delivery and cron job functionality, ensure server resources are adequate, and confirm you’ve selected recipients. Additionally, review any potential server issues or conflicts with third-party plugins. For assistance, contact your provider if you hit sending limits.
Email delays may lead to server timeouts and inaccurate statistics. If you receive a notification, it could be temporary and may resolve itself. For recurring issues, consider increasing your server’s memory limit or reducing the number of emails sent at once in newsletter settings.
Ensure your email campaigns are sent correctly by properly setting up your cron. You can use WP-cron for automatic scheduling or opt for a real cron job for more control. Check your host’s guidelines for setup and troubleshooting to ensure smooth operation.