Hi @kcjpro, we appreciate your feedback here.
I am a software engineer for the WooPayments product. I’d like to iterate on this issue.
They disabled the Woocommerce Payments plugin which was making a loop process with event polling.
Besides what @csmcneill asked above, based on the initial assessment, it might be related to our Webhook Reliability service (feature), which was introduced over one year ago (March, 2022).
Allow me to explain a bit about this service. As you can see in my reference link, we carefully designed this feature to ensure that sites will only use this feature if our WPcom/WCPay server can not deliver webhook events to your site in the first time. It will stop when there is nothing more to fetch. Furthermore, those fetching actions are executed from Action Scheduler (embedded in Woo core), which would optimize this process. Note: I would call them “fetch” rather than “poll” as client sites just fetch them when they need, not always “poll” to send requests.
In fact, some of our largest merchants sometime also need to use this service, but we have not got this type of performance report so far due to this feature alone.
It’s not possible to tell the exact cause at the moment. However, it sounds like if this Webhook Reliability service causes the issue, the hosting can play a vital role here when interacting with our server, i.e. requests in and out from the hosting. Even if that’s the case, we’d like to learn more about that.
Anyway, they’re all our initial assessments, our implementations might not be perfect, and we strive to make WooPayments work flawlessly for everyone. If you can provide additional information for debugging, that would be great. You can safely provide your site information here https://woocommerce.com/my-account/create-a-ticket/ – at least the site address or the WCPay account ID would help.
We also created a GitHub issue to track your report: https://github.com/Automattic/woocommerce-payments/issues/6834
