WooCommerce can continue accepting orders even when transactional emails stop reaching store administrators or customers. In this case, new orders were still being created, but order notifications stopped arriving and a WooCommerce test email failed. The incident coincided with a known Mailgun outage. Later testing confirmed that both the WooCommerce email test and the Mailgun API test were successful again, and normal notifications resumed. No site-level code or configuration change was documented.
Issue background
A WooCommerce store reported that order confirmation emails stopped arriving after a specific point in the evening.
The store itself remained operational:
- Customers could still place orders.
- WooCommerce continued recording the transactions.
- The failure affected email notifications rather than checkout or payment processing.
A test sent from the WooCommerce backend also failed, confirming that the issue was broader than one missing order email.
Diagnosis
The initial task noted that the relevant WooCommerce plugins were up to date. The site was not yet on the newest hosting environment, but the task did not establish that as the cause.
Internal comments identified a known Mailgun outage as the most likely explanation. The site appeared to use Mailgun for transactional delivery, so a service disruption could prevent WooCommerce messages from leaving the website even while orders continued processing normally.
The task did not document a plugin update, DNS change, SMTP repair, API-key replacement, or code deployment. Later tests simply began succeeding again:
- The WooCommerce test email was delivered.
- The Mailgun API test returned a successful result.
- The store confirmed that order emails were arriving again.
Based on the available evidence, the issue was consistent with a temporary third-party email-service interruption, but the task did not independently prove a single root cause.
Resolution steps
- Confirm that orders are still being created. Check WooCommerce orders before treating the incident as a checkout failure.
- Send a WooCommerce test email. Use the available email-testing tool or resend a controlled notification to determine whether the problem affects all transactional mail.
- Check the transactional email provider. Review Mailgun’s service status and incident history for the time the failures began.
- Run a Mailgun API test. Confirm whether the site can authenticate and submit a message successfully through the configured API.
- Review Mailgun logs. Look for accepted, rejected, failed, bounced, or suppressed messages associated with the affected time window.
- Inspect WooCommerce logs. Check for email-generation errors, failed hooks, PHP exceptions, or plugin messages.
- Verify the recipient settings. Confirm that the WooCommerce notification is enabled and that the administrator or customer address is correct.
- Check spam and suppression lists. A valid message may be accepted by the provider but blocked because of a bounce, complaint, suppression, or recipient-side filter.
- Verify domain authentication. Confirm that SPF, DKIM, and any required tracking or return-path records remain valid.
- Avoid unnecessary site changes during an active outage. Do not rotate API keys, replace plugins, or alter DNS unless testing points to a local configuration problem.
- Retest after service recovery. Run both the WooCommerce test and the Mailgun API test again once the provider reports improvement.
- Verify a real order notification. Confirm that a new or test order generates the expected administrator and customer emails.
- Reconcile missed notifications. Review orders placed during the outage and resend any messages that staff or customers still need.
- Add monitoring. Configure delivery alerts or periodic transactional-email tests so failures are discovered before a customer reports them.
A successful WooCommerce order does not confirm that its email was delivered. Checkout, email generation, API submission, and final recipient delivery are separate stages and should be tested independently.
Final outcome
Follow-up testing showed that WooCommerce test emails were sending correctly and the Mailgun API test was successful. The store also confirmed that order notifications had resumed.
No site-level repair was documented in the task. The timing and internal notes were consistent with recovery from a temporary Mailgun service interruption.
The key lesson is to verify the external email provider before making broad WordPress changes. When orders continue processing but all transactional mail stops at once, provider status, API connectivity, and delivery logs are often the fastest path to an accurate diagnosis.
For help troubleshooting WooCommerce email notifications, Mailgun delivery, or WordPress transactional email monitoring, contact Freshy.
