A test order failed, could not run, or the schedule switched off
What each test order result means, the usual reasons a test could not run, and how to switch scheduled test orders back on.
On this page
Could not run
The test could not run because of how the site is set up. It is not a checkout failure, no issue is raised and no failure email is sent.
| Message | What to do |
|---|---|
| WooCommerce is not active | Activate WooCommerce. There is no checkout to test without it. |
| Create the test product first | Create the test product on the Test order screen. |
| Guest checkout is turned off | Turn guest checkout on in WooCommerce → Settings → Accounts & Privacy. The test order is placed as a guest. |
| A test order is already running | Wait a minute and try again. |
| The site could not reach itself | Your host, a firewall, HTTP basic authentication or an IP block stops the site requesting its own pages. Allow the server’s own address, or accept that test orders cannot run on this host. |
| Something hides the test payment method | A plugin that limits payment methods is hiding it. Check its rules for hidden or unknown methods. |
| Shipping is set up (PRO) | The test product is physical but no shipping zone has a working method. Add one, or regenerate the test product as virtual. |
| Update the free plugin (PRO) | PRO test orders need the free plugin, version 1.5.0 or newer. |
Failed
A step that checks your checkout did not work. The result names the step and what was seen. The usual ones:
- The checkout page loads with a checkout form. The checkout page answered, but no checkout form was on it. Open the page in a private window and check the page content and any page builder or caching rule.
- The order is placed through the checkout. The checkout refused the order or returned an error. The message shown is what the checkout said. A plugin that adds checkout rules, such as required fields or order limits, is a common cause.
- A shipping rate is offered (PRO). No rate matched the test address. Check your shipping zones.
- The order matches what the cart promised (PRO). The order total or items differ from the cart. Check plugins that change prices or fees at checkout.
A failed scheduled run raises the issue “The scheduled test order failed” and sends an email under the usual rules. Fix the cause and the next passing run resolves the issue.
The schedule switched itself off
PRO switches the schedule off, shows a red notice on the Test orders screen, raises the issue “Scheduled test orders were switched off” (High) and emails you when:
- a test order could not be fully removed, or PRO found something left behind after a run, so it stops instead of leaving more; or
- the test product is missing.
- Read the notice and the latest run on the Test orders screen. It names the table where something was left behind.
- Press Delete test orders (or Delete all test orders) to remove leftovers, and recreate the test product if it is missing.
- Run a test order by hand and confirm it passes.
- Switch the schedule on again.
The switch is disabled
The reason is shown next to it: the free plugin needs updating, the test product has to be created, a manual test order has to be run and the warnings confirmed, a manual test order has to pass with the current test product, or the PRO license is not active.
I did not get an email
- Manual runs never send email. Only scheduled runs do.
- A failure that repeats keeps the same issue open and does not email again.
- Check your alert recipients and the lowest severity you chose in PRO settings. These issues are High, so choosing Critical only or Off stops the email.
- PRO sends at most 10 issue emails a day.
See PRO test orders and the schedule for the full table, and Why didn’t I receive a critical issue email? for general email checks.
Still need help?
Search the docs first — or open a ticket and our team will pick it up from the Support screen.