Hi @Jon, I think I understood better your question now.
I notice the following difference in behaviour between “Editors (listening)” mode and “Productions” mode.
The Woo Triggering issue seems to be on the “Editors” mode. Although it’s well in listening mode, it does not trigger. The logbook on Woocommerce shows a correct Delivery ID but the response array sometimes shows code 404 and message Not Found.
In the webhook URL generated by n8n, I can see webhook instead of webhook-test
Another remark for Editors mode:
Sometimes, the n8n web display does not show a trigger but the backend has triggered correctly.
This can be misleading and give the impression of no consistent trigger in Editors mode.
A 404 is unusual but if the webhook in Woo does show webhook-test it would only work when you press execute workflow and only the once. If you activate the workflow in n8n then enable the execution logging for the workflow it would be interesting to see if the workflow actually errors.
Is Woo installed on the same server or somewhere else?
It could be that n8n is restarting for some reason and that is why the url is showing as a 404, I would start with the execution logging and maybe checking the docker log to see if there are any errors reported.