Woocommerce order update webhook fires too many times

Hi there @jeffersonmartins ??

Thank you for reaching out. I’d be happy to help you with this!

The Webhook delivery, for order update, is being triggered several times incorrectly, by customers who served months ago and did not make new recent purchases.

From what I gather, there is a custom webhook set up (via an order status plugin, or custom code), that is triggered multiple times. Correct?

Did you already have a chance to reach out to its support channel regarding this, or otherwise?

I hope this is helpful! Please let us know if you have any further questions about this matter, or if we misinterpret your concern in any way. We will be happy to help you further.

I apologize if I wasn’t very clear, I’m using Google Translate.

I went to this location: WooCommerce > Status > Logs

Whenever the order.updated Webhook is triggered, my client receives a message (from an external application).

The problem is that Woocommerce is sending these order.updated Webhooks to customers who haven’t taken any action today (who purchased months ago).

Hello @jeffersonmartins,

The order.update webhook is designed to trigger whenever there’s a modification in order metadata or if a refund is issued so one of your plugins might be triggering these actions in the background.

To help us get a better understanding of what caused the trigger, could you kindly share a recent webhook log from when this started happening? You can locate these logs by navigating to WooCommerce → Status → Logs.

Link to image: https://d.pr/i/PaTRpG

Please make sure to redact any sensitive customer data like emails and address lines before copying the logs into Pastebin.

It would also be greatly helpful if you could specify the exact order ID where this issue occurred.

Look forward to hearing back from you.

thank you for the answer.

See if you can view the information you need: https://pastebin.com/BXjFftfa

Hey, @jeffersonmartins!

Thank you for providing this.

Do you mind sharing more information so we can assist you further?

You mentioned the webhook is triggered several times, right? And from what I understand this happened to more the one customer, correct?

Did you find any similarities on the orders where this happened?

Did you find any patterns of when this happens? Does it happen when you do something specific on the website or does it seem to be random?

How often is this happening?

Have you made any changes to the theme or plugin recentely?

Can you share a screenshot of the order details? Please remove any sensitive information before sharing it.

I’d recommend using https://snipboard.io. You can share the direct link to the image as a response to this topic.

Furthermore, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:

System Status Report which you can find via WooCommerce > Status > Get system report > Copy for support.
Fatal error logs (if any) under WooCommerce > Status > Logs.
You could copy and paste your reply here or paste it via https://gist.github.com/ and send the link here.

Looking forward to your reply.

Have a wonderful day!

Hello, I would like to revisit this issue because it keeps happening.

You said the webhook is triggered multiple times, right? And from what I understand, this happened to another customer, correct?
Correct. And there seems to be a connection between them.

Did you find any similarities in the orders where this happened?
Not until now.

Have you found any patterns for when this happens? Does this happen when you do something specific on the site or does it seem random?
Not until now.

How often is this happening?
It still happens every day, about XX times a day, with random customers.

Have you made any changes to the theme or plugin recently?
Since the first post, we have changed the server and updated several plugins and themes, but the problem persists.

Can you share a screenshot of the order details? Remove any confidential information before importing it.
What details do you need to be shared?

I would like to take this opportunity to share part of the log between the periods in which the webhook was triggered:

The customer received the notice at 7:37 pm – https://vemaprenderbrincando.com.br/wp-content/uploads/2024/03/1-06-Mar-2024-193600-UTC-PHP-Deprec.txt
The customer received the notice at 4:01 pm – https://vemaprenderbrincando.com.br/wp-content/uploads/2024/03/2-07-Mar-2024-160021-UTC-PHP-Deprec.txt
The customer received the notice at 11:18 pm – https://vemaprenderbrincando.com.br/wp-content/uploads/2024/03/3-07-Mar-2024-231715-UTC-Erro-de-ev.txt

Hi there

Thanks for including those error logs; Based on the timestamps you shared and cross-referencing that with the logs, it looks like this might be linked to the ActiveCampaigns for WooCommerce plugin (the logs indicate some deprecated code being used). Are you still seeing the same thing when that plugin is disabled?

I deactivated the ActiveCampaigns plugin for WooCommerce and the problem remains

[12-Mar-2024 20:10:45 UTC] Erro de evento n?o agendado do cron para o gancho: remove_expired_pix_asaas, código de erro: could_not_set, mensagem de erro: N?o foi possível salvar a lista de evento do cron, dados: {"schedule":false,"args":[{"refunds":null}]}
[12-Mar-2024 20:10:45 UTC] Erro de evento n?o agendado do cron para o gancho: remove_expired_pix_asaas, código de erro: could_not_set, mensagem de erro: N?o foi possível salvar a lista de evento do cron, dados: {"schedule":false,"args":[{"refunds":null}]}
[12-Mar-2024 20:10:45 UTC] Erro de evento n?o agendado do cron para o gancho: remove_expired_pix_asaas, código de erro: could_not_set, mensagem de erro: N?o foi possível salvar a lista de evento do cron, dados: {"schedule":false,"args":[{"refunds":null}]}
[12-Mar-2024 20:10:45 UTC] PHP Deprecated:  version_compare(): Passing null to parameter #2 ($version2) of type string is deprecated in /home/u279936711/domains/vemaprenderbrincando.com.br/public_html/wp-content/plugins/elementor/core/experiments/manager.php on line 167
[12-Mar-2024 20:10:45 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/u279936711/domains/vemaprenderbrincando.com.br/public_html/wp-content/plugins/elementor-pro/modules/loop-builder/module.php on line 200
[12-Mar-2024 20:10:46 UTC] PHP Deprecated:  version_compare(): Passing null to parameter #2 ($version2) of type string is deprecated in /home/u279936711/domains/vemaprenderbrincando.com.br/public_html/wp-content/plugins/elementor/core/experiments/manager.php on line 167
[12-Mar-2024 20:10:46 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/u279936711/domains/vemaprenderbrincando.com.br/public_html/wp-content/plugins/elementor-pro/modules/loop-builder/module.php on line 200
[12-Mar-2024 20:10:50 UTC] PHP Deprecated:  version_compare(): Passing null to parameter #2 ($version2) of type string is deprecated in /home/u279936711/domains/vemaprenderbrincando.com.br/public_html/wp-content/plugins/elementor/core/experiments/manager.php on line 167
[12-Mar-2024 20:10:50 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/u279936711/domains/vemaprenderbrincando.com.br/public_html/wp-content/plugins/elementor-pro/modules/loop-builder/module.php on line 200
[12-Mar-2024 20:10:51 UTC] PHP Deprecated:  version_compare(): Passing null to parameter #2 ($version2) of type string is deprecated in /home/u279936711/domains/vemaprenderbrincando.com.br/public_html/wp-content/plugins/elementor/core/experiments/manager.php on line 167
[12-Mar-2024 20:10:51 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/u279936711/domains/vemaprenderbrincando.com.br/public_html/wp-content/plugins/elementor-pro/modules/loop-builder/module.php on line 200
[12-Mar-2024 20:10:51 UTC] Erro de evento n?o agendado do cron para o gancho: remove_expired_pix_asaas, código de erro: could_not_set, mensagem de erro: N?o foi possível salvar a lista de evento do cron, dados: {"schedule":false,"args":[{"refunds":null}]}
[12-Mar-2024 20:10:51 UTC] Erro de evento n?o agendado do cron para o gancho: remove_expired_pix_asaas, código de erro: could_not_set, mensagem de erro: N?o foi possível salvar a lista de evento do cron, dados: {"schedule":false,"args":[{"refunds":null}]}
[12-Mar-2024 20:10:51 UTC] Erro de evento n?o agendado do cron para o gancho: remove_expired_pix_asaas, código de erro: could_not_set, mensagem de erro: N?o foi possível salvar a lista de evento do cron, dados: {"schedule":false,"args":[{"refunds":null}]}

Hi @jeffersonmartins,

From the logs, it looks like the issue is related to the Elementor and Elementor Pro plugins you’re using. The logs indicate that the version_compare() and strpos() functions are receiving null values, which is causing deprecated warnings.

I recommend updating Elementor and Elementor Pro to the latest versions if you haven’t already done so. Also, try deactivating and reactivating these plugins to see if the issue persists.

The logs also show errors related to the remove_expired_pix_asaas cron event, which seems to be unable to save the event list. This could be related to a specific plugin that handles these events or a custom code snippet. You may need to check any plugins or custom code that could be creating these events.

I hope this provides some clarity. Please let us know if you have any other questions!