Hi Rithika,
Thanks for the detailed run history, which made this much faster to pin down. This is a genuine bug on our side rather than anything misconfigured on your store, and we reproduced it here today. Your 600 figure matches it exactly.
What is happening: your feed builds in batches of 200. If a scheduled run starts while a previous run is still partway through, the plugin can misread the running feed as a stalled one, reset it, and start a second build over the same file. The second build appends rather than replacing, so you end up with 200, plus 200 repeated, plus 200, which is the 600 you are seeing. Manual regeneration is always correct because nothing else is running at that moment.
You can confirm it on your own site. Open WooCommerce → Status → Logs, pick the woo-product-feed-pro log for one of the 600 products, and look for “Feed appears stuck (processing with no pending batches), allowing reset”. If that line is there, this is the bug firing.
Two things will reduce it until the fix ships:
- Go to Product Feed → Settings → General, tick Change products per batch number, and set Insert batch size to 600. Your whole feed then builds in a single pass, which removes most of the window where this can happen. It also switches off a second route that can trigger it. If generation starts timing out on your host, lower the number again.
- On the feed’s General tab, check Refresh interval. If it is set to Hourly or Twice Daily, moving it to Daily gives each run more room to finish. Let me know what yours is currently set to, as that helps us confirm how you are hitting it.
One thing worth knowing: the same fault can occasionally drop products instead of duplicating them, so a run that looks like a normal 504 is not automatically clean. It is worth spot-checking your channel for missing items as well.
This is with our developers now. I will not guess at a release date, but I will post back here once the fix is out.
Thanks!
Hi,
Thanks for looking into this and for the detailed explanation.
I checked the WooCommerce → Status → Logs and I can confirm that the following message is present: “Feed appears stuck (processing with no pending batches), allowing reset”.
Also, I checked the feed settings, and the Refresh interval is already set to Daily.
Please let me know if there’s anything else I can provide to help with debugging or testing the fix.
Thank you!
Hi Rithika,
That log line settles it, so nothing is misconfigured on your side. Since your refresh interval is already Daily, we can rule out one of the two ways the overlap happens. The other one is the Product Feed page itself: while it is open in a browser tab, the plugin runs feed batches inside that page request. If a scheduled run starts at the same moment, the two collide, and you get the appended duplicates.
So, the batch setting is what to change now, not the interval. Go to Product Feed → Settings → General, tick Change products per batch number, and set Insert batch size to 600. Your whole feed then builds in a single pass, and it also switches off the in-page batch runner, which closes the route above. If 600 turns out to be too heavy and generation starts timing out, lower it and tick Disable HTTP feed generation requests instead, which switches off that runner on its own. That one relies on your host running a real cron job for WordPress, so it is worth checking that first: https://www.adtribes.io/knowledge-base/what-does-disable-http-feed-generation-requests-do/
That should cut the duplicates down a long way, though it narrows the window rather than closing it entirely. The proper fix is with our developers, and I will post back here once it ships. If you can reply in a few days with whether the “Feed appears stuck” line stops appearing, and the counts hold around 507, that is a useful confirmation for us.
One last thing worth keeping an eye on: the same fault can drop products instead of duplicating them, so a run showing a normal 504 is not automatically clean. Worth spot-checking your channel for missing items as well.
Thanks!
As we’ve not received a reply in 24+ hours, I’ll mark this post as resolved. If you still have questions or have other issues please create a new post.