504 Gateway Timeout due to update_products/process_item job
-
Since morning (IST), all of our clients ecommerce sites using ‘Google for WooCommerce’ plugin are facing an issue. The root cause seems to be coming from the scheduled action ‘gla/jobs/update_products/process_item’, which seems to send cURL request to https://api.woocommerce.com/google/google-mc/content/v2.1/products/batch. Here’s the full error message recorded in the action scheduler log.
- 2025-09-27 12:06:19 +0000 action created
- 2025-09-27 12:08:32 +0000 action started via WP CLI
- 2025-09-27 12:10:45 +0000 action failed via WP CLI: Error updating Google products: cURL error 28: Failed to connect to api.woocommerce.com port 443 after 132844 ms: Could not connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://api.woocommerce.com/google/google-mc/content/v2.1/products/batch
This seems to be happening randomly. I guess api.woocommerce.com is facing some reliability issue.
Nevertheless, this error should not take down the entire admin panel with ‘504 Gateway Timeout’ error. Although site works fine for logged out users.
Can plugin authors please look into this issue?
-
Hi there,
Thanks for the details so far. Based on how the Google Listings & Ads extension works, timeouts usually point to either environment limits or network interruptions rather than the plugin itself.
Could you please share your WooCommerce System Status Report with us (WooCommerce → Status → Get system report → Copy for support) along with the approximate number of products being synced?
Paste the System Status Report into https://pastebin.com or https://gist.github.com
This info will help us check your setup and narrow down what’s causing the timeouts.
Hi,
Thank you for taking time to reply. Here’s the WooCommerce System Status Report of one of the affected site: https://pastebin.com/UcgcxL7J (expires in 1 day).
Note: Some identifying information like site URL and database prefixes were replaced with the text “[REDACTED]”.
Hi @hronak,
Thank you for getting back to us. As my colleague mentioned, the issue appears to be related to server resource limits, which can affect API connections and lead to the error you’re seeing.
After reviewing your system status report, here are my recommendations:
- Please increase your WP Memory Limit to 512 MB or even 1 GB. While WooCommerce itself requires at least 256 MB, your site is running several heavy, resource-intensive plugins, and the current 128 MB is too low.
- Increase your PHP Time Limit from the current 60 seconds to at least 300 seconds, to allow enough time for connections and processes to complete.
If you’re not sure how to adjust these settings, I recommend contacting your hosting provider for help, especially for increasing the PHP time limit.
For the memory limit, you can add the following line to your wp-config.php file:
define('WP_MEMORY_LIMIT', '512M');Hey,
Sorry to say that it’s not related to server resource limit. The error is happening randomly since yesterday as mentioned earlier. It was working perfectly all this long. We’ve tried pinging api.woocommerce.com while this error happened on the same machine, it didn’t respond to ping as well. So clearly the endpoint was down it seems.
Our support request is about the ‘cURL error 28’ on api.woocommerce.com taking down the WordPress admin panel. It shouldn’t be happening because those requests are executed in cron jobs from WP-CLI using system cron. Yesterday, admin panel of all our client’s sites with this plugin (Google for WooCommerce) were down due to this error. By down, I mean it kept on loading and them returned 504 gateway timeout.
Can you replicate it on your end by manually triggering timeout and see if takes down the whole WordPress admin panel?
Hi @hronak,
Thank you for getting back and for clarifying the situation. I completely understand how frustrating it can be to run into issues like this, and I want to reassure you that we don’t make assumptions — instead, we troubleshoot step by step to be certain of the cause.
From the error, this does look related to server resources. While that may not be the only factor, it’s the best place to start. At the moment, more than 80% of the plugins on your site are resource-intensive, and with your current memory limit set at 124 MB, the environment doesn’t meet WooCommerce’s minimum requirement of 256 MB. With those extra heavy plugins, I recommend increasing it to 512 MB or even 1 GB, and also raising the PHP time limit to 300 seconds.
Because the issue happens only occasionally, it further suggests that server usage is the likely trigger. Many plugins run background processes and checks at intervals, and when several are active at the same time, they can consume all available resources. If Google for WooCommerce happens to sync at that moment, the site may crash due to insufficient resources.
If this were a widespread problem, we’d be seeing more reports. Since you’re the only one experiencing it, it’s very likely specific to your environment and setup. Working through the troubleshooting this way will help us narrow it down properly and avoid guesswork.
Since morning (IST), all of our clients ecommerce sites using ‘Google for WooCommerce’ plugin are facing an issue
To help us better understand the issue, could you confirm whether all your clients’ websites are hosted on the same server with the same hosting provider, and whether they share resources or each has its own control panel? Also, are you using a multisite setup?
When you reply, please go to WooCommerce > Status > Logs, check the most recent fatal error log, and share it with us via Pastebin.
It’s been a while since we heard back from you for this reason we are closing this thread.
If Google for WooCommerce has been useful for your store and you appreciate the support you’ve received, we’d truly appreciate it if you could leave us a quick reviewhere:
https://wordpress.org/support/plugin/google-listings-and-ads/reviews/
Feel free to open a new forum topic if you run into any other problem.
It happened again today. We ran PING for api.woocommerce.com the moment our admin panel went down and here are the results:
$ ping api.woocommerce.com
PING api.woocommerce.com (192.0.96.246) 56(84) bytes of data.
64 bytes from 192.0.96.246: icmp_seq=1 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=5 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=10 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=12 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=39 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=42 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=43 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=46 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=48 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=49 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=50 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=51 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=52 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=55 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=59 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=61 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=66 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=68 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=70 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=75 ttl=48 time=266 ms
^C
--- api.woocommerce.com ping statistics ---
75 packets transmitted, 20 received, 73.3333% packet loss, time 75554ms
rtt min/avg/max/mdev = 266.100/266.168/266.289/0.050 ms73% packet loss. There’s definitely something going on with api.woocommerce.com. I would love if WooCommerce Site Reliability team can respond here.
Moreover, when wp-cron & action scheduler jobs are run via WP-CLI, IT SHOULDN’T BE TAKING DOWN THE FRONTEND. THAT’S WHAT I’VE BEEN TRYING TO MAKE YOU GUYS UNDERSTAND.
A related issue was posted in Dec, 2023 – https://wordpress.org/support/topic/product-feed-in-wordpress-admin-will-not-load/
Hi @hronak,
Thank you for getting back to us and providing an update. I completely understand how issues like this can be frustrating and overwhelming—it’s natural to feel stressed when things aren’t working as expected. Please be assured that we take your concerns seriously and want to help you resolve this.
That said, to assist effectively, we do need your cooperation. It appears that some of our previous suggestions and requests haven’t been addressed yet. I kindly ask that you review my last two responses and provide clarification regarding the points and questions raised.
As mentioned earlier, this issue seems to be related to server resource availability. From our review of your setup, we’ve noticed a number of server-intensive plugins combined with limited resources. If your site has a large number of products, these kinds of issues can occur.
I look forward to your clarification regarding the suggestions and questions previously asked—such as whether you’ve increased server resources, whether you’re using a multisite setup, or if your clients’ websites are hosted on the same panel. So far, you seem to be the only one reporting this issue. If it were more widespread, we would likely have received additional reports and been able to reproduce the issue ourselves.
Finally, it appears that the issue this time is related to WooCommerce. Your initial request was about Google for WooCommerce—are you saying that the API access in WooCommerce is causing the crash, or that Google for WooCommerce is conflicting with your site and triggering the crash?
Looking forward to your response.
It seems we haven’t heard back from you for a while, so I’ll go ahead and mark this thread as resolved. Feel free to reach out whenever you’re ready to continue.
If you have a few minutes, we’d love if you could leave us a review: https://wordpress.org/support/plugin/google-listings-and-ads/reviews/
The topic ‘504 Gateway Timeout due to update_products/process_item job’ is closed to new replies.