Woocommerce order.updated trigger fires reguarly when order is "on hold"

Questions
1

Describe the problem/error/question

Woocommerce order.updated trigger is firing consistently. order.created is fine, fires once and is all good

I have a test workflow triggered off order.updated. I have 1 order “on-hold” in woocommerce and the order.updated trigger is firing every few minutes (sometimes every 20 seconds, the gap seems to be random). it only fires for the “on-hold” order.

The order isn’t being updated, at least not manually. I took the workflow data json of two trigger invocations and did a diff and the results are identical.

I have noticed that if I turn the workflow on and off, then the update trigger doesn’t fire constantly. However if I actually go into the woocommerce order and make an update (eg add a note), then the trigger immediately fires twice and then continues to fire every few minutes as before.

Please share your workflow

The test workflow I am using is only the woocommerce trigger node. I set it to fire on order.updated and thatss it.

Information on your n8n setup

  • 1.35.0, :
  • Database : SQLite:
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via Docker
  • Debian
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
4

Hey @louiszezeran,

The order.updated will trigger whenever Woo thinks there has been an update, Other than configuring the webhook in Woo though we don’t send the webhook or fetch the data it is sent by Woo whenever the condition is met so it could be that there is a bug with that webhook or there are maybe other updates happening.

5

Thank you for the information

6

I was able to work through the woocommerce webhook logs and see that order.update is being fired too many times from that side

I tried turning plugins on and off until I determined the plugin which was causing the excess order.update events.

thank you again for your help

1 Like
7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.