Skip to content
TutorialOct 2026·8 min read

WooCommerce webhooks not firing: how to check deliveries

WooCommerce switches a failing webhook off without telling you. Find the cause in the delivery log and Action Scheduler, then test the URL with a request bin.

SmartWP teamThe people who build our plugins
Flat illustration of a broken line between a store and an app with a packet stuck

Level

Intermediate

Steps

5

Time

About 15 minutes

You’ll need

Admin access to WooCommerce, and access to the app or server that receives the webhook

When a WooCommerce webhook is not working, open WooCommerce → Settings → Advanced → Webhooks and check its status first. Disabled means WooCommerce switched it off after too many failed deliveries in a row. If it says Active, read its delivery log for the response code, then look for deliveries stuck in Action Scheduler.

How WooCommerce sends a webhook

A webhook is a message your store sends to another app when something happens, such as a new order. The app gives you a URL, and WooCommerce posts the order’s details to it as JSON.

The message doesn’t leave straight away. WooCommerce waits until the request that triggered it has finished, then hands the delivery to Action Scheduler, its background job queue, as a job named woocommerce_deliver_webhook_async.

When that job runs, WooCommerce builds the payload, sends it and waits up to 60 seconds for an answer. Any 2xx response counts as delivered, and so does a 301 or 302 redirect. Everything else is a failure, timeouts included.

WooCommerce webhook not working? Check if it’s disabled

The Webhooks screen lists each webhook with its status. Active ones deliver, and Paused ones were turned off by hand. Disabled means WooCommerce turned it off itself because deliveries kept failing.

WooCommerce counts failures in a row, and one successful delivery resets the count to zero. Its documentation says webhooks are disabled after five retries. In the current code the count has to pass five first, so the seventh failure in a row is the one that switches it off.

WooCommerce doesn’t email you or show a notice when this happens. The first sign is usually an order that never reached your shipping app or CRM.

Find the cause in the delivery log before you switch it back on. WooCommerce keeps the failure count when you re-enable a webhook, so one more failed delivery disables it again. Once the cause is fixed, open the webhook, set Status to Active and click Save webhook.

If the receiving app has planned downtime, a developer can allow more failures with WooCommerce’s woocommerce_max_webhook_delivery_failures filter. It only buys time: a URL that keeps failing still gets switched off.

PHP
// Let a webhook fail more times in a row before WooCommerce disables it.
add_filter( 'woocommerce_max_webhook_delivery_failures', function () {
	return 10;
} );

Read the webhook delivery logs

WooCommerce logs every delivery attempt. Go to WooCommerce → Status → Logs, pick webhooks-delivery in the source filter and open the newest file. Each entry has the delivery URL, how long the request took, the headers WooCommerce sent and the response it got back.

The request and response bodies are only written when WP_DEBUG is on, which keeps customer details out of the log. You rarely need them, because the response code and message tell you most of the story.

Response in the log What it means and what to do
Any 2xx code Delivered. If the other app shows nothing, look at its own logs and filters.
301 or 302 WooCommerce counts this as delivered, but it doesn’t follow redirects, so the data never reached the app. Use the final URL, often the https version or the one with a trailing slash.
401 or 403 The app or a firewall in front of it refused the request. Check the app’s API key and signature settings.
404 or 410 The URL doesn’t exist any more. The flow or integration on the other side was probably deleted or switched off.
Any 5xx code The app crashed or was overloaded. Its own error log will say why.
http_request_failed with “A valid URL was not provided.” WordPress blocked the URL because it points to a private address, such as localhost, or uses a port other than 80, 443 or 8080. Give the app a public HTTPS address.
http_request_failed with “cURL error 28” The app took longer than 60 seconds to answer. It should reply at once and do the slow work afterwards.

No webhooks-delivery entries at all? Open the log Settings. Logging has to be enabled, and the Level threshold has to let Info entries through, since that’s the level deliveries are logged at. If both are fine and the log is still empty, the deliveries never ran.

Find stuck deliveries in Action Scheduler

Deliveries that never reached the log are in the background queue, either still waiting or failed before they could send. Go to WooCommerce → Status → Scheduled Actions and search for woocommerce_deliver_webhook_async.

  • A pile of Pending deliveries, some marked past due, means the queue has stalled. Action Scheduler mostly runs on WP-Cron, so a site with WP-Cron switched off and no server cron job in its place falls behind.
  • Failed deliveries show the reason in the Log column. “Unsupported webhook API version” means the webhook still uses the Legacy REST API, which WooCommerce took out of core in version 9.0. Edit the webhook, choose WP REST API Integration v3 under API Version and save. Add webhooks to the checks you run before a major WooCommerce update.
  • A long backlog of other pending actions delays everything queued behind it, webhooks included. Our guide to past-due and failed scheduled actions explains how to clear it.

Quick edits can look like missing updates. If an order changes again while its delivery is still pending, WooCommerce doesn’t queue a second job. The pending job sends the order as it is when it runs, so the app gets a single update with the latest details.

With WP-CLI on the server, you can count the deliveries and run the ones that are due:

WP-CLI
# Count webhook deliveries waiting in the queue, then the failed ones
# (--per_page=0 lifts Action Scheduler's default limit of 5 results)
wp action-scheduler action list --hook=woocommerce_deliver_webhook_async --status=pending --per_page=0 --format=count
wp action-scheduler action list --hook=woocommerce_deliver_webhook_async --status=failed --per_page=0 --format=count

# Run the webhook deliveries that are due now
wp action-scheduler run --group=woocommerce-webhooks
A tray catching envelopes as they arrive
A request bin shows exactly what your store sends, and when.

Test the webhook with a request bin

A request bin is a throwaway URL that records every request sent to it. Point a test webhook at one and you’ll know which side is at fault: if the bin gets the order and your app doesn’t, the problem is in the app.

  1. 01

    Create a bin

    Open Webhook.site and copy the unique URL it gives you. It answers every request with a 200 by default, which is the answer WooCommerce wants.

  2. 02

    Add a test webhook

    Go to WooCommerce → Settings → Advanced → Webhooks and click Add webhook. Give it the same Topic as the webhook that isn’t working, paste the bin URL into Delivery URL, set Status to Active and click Save webhook.

  3. 03

    Watch for the ping

    Saving an active webhook makes WooCommerce send a short test ping to the URL. Its body is just webhook_id= and the webhook’s ID, with no signature, and only a 200 answer counts as a pass.

  4. 04

    Trigger a real event

    Place a test order or edit a product, whichever matches the topic. When the queue next runs, the bin shows a JSON request with headers such as X-WC-Webhook-Topic and X-WC-Webhook-Signature.

  5. 05

    Compare, then clean up

    If the bin got the delivery and your app didn’t, check the URL, keys and logs on the app’s side. If the bin got nothing either, go back to Action Scheduler. Delete the test webhook when you’re done.

A run of pipes with one valve closed
A firewall, a code filter or a disabled hook can stop the whole flow.

Other reasons a webhook stops firing

  • The user who created the webhook was deleted or lost access. WooCommerce builds every payload as that user, so deliveries arrive with an error message where the order should be. The settings screen has no field to change the user, so recreate the webhook while logged in as an admin who’s staying. Copy the old webhook’s Secret into the new one, so the app still accepts the signature.
  • The topic is narrower than it looks. Order created fires once, when the order is created. Later changes, such as Processing to Completed, go out as Order updated, so a webhook on Order created alone never hears about them.

See every webhook’s health on one screen

Going through three screens works, but it’s slow when orders are already going missing. Admin Powerups for WooCommerce has a Webhook health power-up that brings these checks into one tab.

  • Each webhook gets a health label, such as Disabled, Failing with its count so far, Paused, Owner missing or No successful ping yet. Disabled and failing ones come first.
  • Recent deliveries show the response and duration, read from WooCommerce’s own webhooks-delivery log.
  • The delivery queue shows how many jobs are waiting or failed, and how late the oldest one is.
  • Send test sends WooCommerce’s own ping without touching the failure count. Re-enable switches a disabled webhook back on after a second click and starts its failure count from zero.

The tab shows only the host of each delivery URL, never the full address, secret, signature or payload, and the power-up stores nothing of its own. It’s off until you switch it on, and only site admins see it. The Webhook health docs explain each label.

Keep reading