Hi @pbradstreet
Can you add the code in here, so we can try it on our end?
Hi, Sorry which code are you referring to?
I am selecting “order-updated” in WooCommerce/Settings/Advanced/Webhooks.
dougaitken
(@dougaitken)
Automattic Happiness Engineer
Hey @pbradstreet
I’ve tried this myself, both with a new customer order created from the front-end and then updating an existing order from Processing to Completed via the official WooCommerce Mobile app.
I then checked my webhook logs after each and the webhook was triggered as expected. I also checked for bulk updating order status and manually changing the order status from within an order – again, all showing as expected.
There is no log entry so this is a tough one to troubleshoot.
If the webhook is active and there are no logs, this is likely caused by a conflict with your theme or with another plugin. Read more about plugin and theme conflicts in our Self-Service Guide.
For more detailed instructions about conflict testing, check out this – How to test for plugin and theme conflicts.
Please let us know how that goes.
Thanks,
Hi, thanks very much for your response. As it turns out I finally fixed the issue yesterday. It turns out that the issue was more related to my application that received the webhook post. We are using WordPress multisite and I use the collection url to know which client website the webhook was submitted by. If the Collection url did not match my stored client collection url in our app it returns an error since that means that the submission did not come from a valid client.
The actual issue if anyone ever has a similar issue is that the automatically fired webhook uses the resolved domain name but if you manually update the order fire the webhook, the submitted collection url is the sub-domain version of the url. So I now compare to both possible variations of the collection url and it is working perfectly now.
