Conversation
supportI see something awkward; see screenshot: https://share.woofers.be/xQuX48xX Feed: https://www.stropellets.be/wp-content/uploads/wppfm-feeds/stropulver-feed.xml When i download and view the feed, it seems normal. Also in Google Shopping i don’t see any issues, so Google can read it; i guess. Just 3 products in feed, no mulitple feed generation at once. Any idea why i see what i see in the screenshot? Regenerating it manually solves it. And it only happens with 3 out of 4 product feeds. Logfile/ [2026-06-16 01:00:24]-[MESSAGE]=Generating feed 2 through a cron initiated in background mode. [2026-06-16 01:00:24]-[MESSAGE]=Feed 2 is a google feed writing to /////wp-content/uploads/wppfm-feeds/stropulver-feed.tmp.xml (final publication path ///wp-content/uploads/wppfm-feeds/stropulver-feed.xml), with an original feed status 4. [2026-06-16 01:00:24]-[MESSAGE]=Pushed 3 products in the feed queue [2026-06-16 01:00:24]-[MESSAGE]=The feed status of feed 2 has been set to Processing (3) [2026-06-16 01:00:24]-[MESSAGE]=Issued async nonce (request_id=req_6a30a028a78333.27833798, created=1781571624, identifier=wppfm_feed_generation_process). [2026-06-16 01:00:24]-[MESSAGE]=Feed Update dispatched. Dispatched url = https://www.stropellets.be/wp-admin/admin-ajax.php?action=wppfm_feed_generation_process&nonce=958c3d25b8&feed_id=2 Dispatched blocking = Dispatched sslverify = Dispatched args body = empty Dispatched args cookie = empty [2026-06-16 01:00:24]-[MESSAGE]=Dispatching async request via wp_remote_post (blocking=false, timeout=30s, url=https://www.stropellets.be/wp-admin/admin-ajax.php?action=wppfm_feed_generation_process&nonce=958c3d25b8&feed_id=2). [2026-06-16 01:00:25]-[MESSAGE]=wp_remote_post returned (code=n/a, message=n/a, blocking=false). [2026-06-16 01:00:25]-[MESSAGE]=Response on dispatched (wp_remote_post) call is -> code: no response code, message: no response data [2026-06-16 01:00:25]-[WARNING]=Feed watchdog (stale_processing_flag) activating feed 2. [2026-06-16 01:00:25]-[WARNING]=Appending to the existing feed log because feed 2 restarted within the last 3600 seconds. [2026-06-16 01:00:25]-[MESSAGE]=Generating feed 2 through a cron initiated in background mode. [2026-06-16 01:00:25]-[MESSAGE]=Feed 2 is a google feed writing to /////wp-content/uploads/wppfm-feeds/stropulver-feed.tmp.xml (final publication path //////wp-content/uploads/wppfm-feeds/stropulver-feed.xml), with an original feed status 3. [2026-06-16 01:00:25]-[MESSAGE]=Pushed 3 products in the feed queue [2026-06-16 01:00:25]-[MESSAGE]=The feed status of feed 2 has been set to Processing (3) [2026-06-16 01:00:25]-[MESSAGE]=Issued async nonce (request_id=req_6a30a029974306.03383789, created=1781571625, identifier=wppfm_feed_generation_process). [2026-06-16 01:00:25]-[MESSAGE]=Feed Update dispatched. Dispatched url = https://www.stropellets.be/wp-admin/admin-ajax.php?action=wppfm_feed_generation_process&nonce=958c3d25b8&feed_id=2 Dispatched blocking = Dispatched sslverify = Dispatched args body = empty Dispatched args cookie = empty [2026-06-16 01:00:25]-[MESSAGE]=Dispatching async request via wp_remote_post (blocking=false, timeout=30s, url=https://www.stropellets.be/wp-admin/admin-ajax.php?action=wppfm_feed_generation_process&nonce=958c3d25b8&feed_id=2). [2026-06-16 01:00:26]-[MESSAGE]=wp_remote_post returned (code=n/a, message=n/a, blocking=false). [2026-06-16 01:00:26]-[MESSAGE]=Response on dispatched (wp_remote_post) call is -> code: no response code, message: no response data [2026-06-16 01:01:12]-[MESSAGE]=Feed handle has been started. Async request has been passed through. [2026-06-16 01:01:12]-[MESSAGE]=Started a new batch with 256M memory available. The stored batch still contains 4 items [2026-06-16 01:01:12]-[MESSAGE]=Started processing product 2550 [2026-06-16 01:01:12]-[MESSAGE]=Started processing product 2556 [2026-06-16 01:01:12]-[MESSAGE]=Started processing product 8926 [2026-06-16 01:01:12]-[MESSAGE]=Preserved feed context for completion (properties key: wppfm_feed_generation_process_batch_2_735ce42994a46de98878d78cfb) [2026-06-16 01:01:12]-[MESSAGE]=Preserved feed context for completion (properties key: wppfm_feed_generation_process_batch_2_735ce42994a46de98878d78cfb) [2026-06-16 01:01:12]-[MESSAGE]=No more products in the batch, so we can clear the batch data from the site options. Used key = wppfm_feed_generation_process_batch_2_735ce42994a46de98878d78cfb [2026-06-16 01:01:12]-[MESSAGE]=Feed handle has been started. Async request has been passed through. [2026-06-16 01:01:12]-[MESSAGE]=Started a new batch with 256M memory available. The stored batch still contains 4 items [2026-06-16 01:01:12]-[MESSAGE]=Started processing product 2550 [2026-06-16 01:01:12]-[MESSAGE]=Started processing product 2556 [2026-06-16 01:01:12]-[MESSAGE]=Started processing product 8926 [2026-06-16 01:01:12]-[MESSAGE]=Preserved feed context for completion (properties key: wppfm_feed_generation_process_batch_2_1e7747d2e7a458333a2357a9d6) [2026-06-16 01:01:12]-[MESSAGE]=Preserved feed context for completion (properties key: wppfm_feed_generation_process_batch_2_1e7747d2e7a458333a2357a9d6) [2026-06-16 01:01:12]-[MESSAGE]=No more products in the batch, so we can clear the batch data from the site options. Used key = wppfm_feed_generation_process_batch_2_1e7747d2e7a458333a2357a9d6 [2026-06-16 01:01:12]-[MESSAGE]=Queue is empty, preparing to finalize feed completion [2026-06-16 01:01:12]-[MESSAGE]=Feed context already available, no restoration needed [2026-06-16 01:01:12]-[MESSAGE]=Acquired completion lock (key=wppfm_feed_completion_lock_2, ttl=600s). [2026-06-16 01:01:12]-[MESSAGE]=Started the complete function to clean up the feed process and queue. [2026-06-16 01:01:12]-[MESSAGE]=The feed status of feed 2 has been set to OK (1) [2026-06-16 01:01:12]-[MESSAGE]=Completed feed 2. The feed should contain 3 products and its status has been set to 1. [2026-06-16 01:01:12]-[MESSAGE]=The feeds url = https://www.stropellets.be/wp-content/uploads/wppfm-feeds/stropulver-feed.xml.
Hi @davelo , The issue is that the feed has two feeds in one. If you open the feed in your browser, then right click on it and select “view page source” you get the raw xml page. In that view you’ll see that on row 61 the xml code closes the feed but also again starts to open it. It is as if the feed data has been written twice to the same file. You say that if you manually regenerate the feed it is ok again. Does that mean that the failure only occurs when you regenerate the feed in auto mode?
Hi Michel, good insight looking at the raw xml strange. Mmm strange. It only happens indeed with the auto mode. Not on the manual regenerate. But then again: it happens not always. I have 4 feeds of 3 products. This morning only one was “corrupt”. I use your plugin on a lot of shops, also the premium plugin. I have not seen this issue before. But this shop is also hosted on another server (not mine or in my control) and with other caching plugins then i’m used too. I’m thinking it should have something to do with caching. There are 2 plugins: Litespeed and Super Page Cache (for Cloudflare). So, i’m going to do some more tests. I keep you informed.
Dave, strange indeed. Can you confirm you’re using the latest version on that specific shop?
Yes, Version 2.23.6
Hi @davelo , Can you try the following: Open the Feed Manager -> Settings page and activate the “Feed process logger” option Then wait for a feed to fail. Once one has failed, do not (yet) regenerate it. Instead: Open the wp-content/uploads/wppfm-logs folder on your server Make a copy of all the log files in that folder and send them to michel (at) wpmarketingrobot.com, refering to this topic. Once you’ve done that you can manually regenerate the feed again. Once I have the logging files I could try to identify the possible cause and might be able to harden the auto feed update process.
Hi Dave, Did you get my previous reply?
Hi Michel, Yes, i was waiting on your reply. 🙂 I sended the logs on 20 june. I’ll send them now again.
Hi Dave, I’m not receiving the mails. Might be that my mail service is blocking the extentions of the files you send. Could you send me an email without files so I can reply to you with another suggestion on how to transfre the files?
Hi Dave, I still haven’t received your mail. I don’t know why your mails are not coming through, but lets try a different approach. Can you please open a ticket here: https://www.wpmarketingrobot.com/support/ and let me know when you entered it so I can assign it to myself?
Hi Dave, I received the files now. Thanks! I will have a look at them just to see if there is an issue I can identify an improve on. I will let you know.
Hi Dave, Thanks for sending the logs. Unfortunately, they indicate that the feed generation is working correctly. The issue is that each feed regeneration overwrites the previous logs, and it appears that a successful regeneration was the most recent logged event. Since you mentioned that the feeds are currently regenerating without problems, I recommend leaving the feed logger enabled until the issue occurs again. If a feed fails, please disable the logger immediately (or make a copy of the log files), then manually regenerate the feeds and send me the updated logs. For now, I will close your ticket. With a bit of luck, this was just a one-time hiccup. Please feel free to reopen the ticket if the issue returns.
Hi @davelo , The issue is that the feed has two feeds in one. If you open the feed in your browser, then right click on it and select “view page source” you get the raw xml page. In that view you’ll see that on row 61 the xml code closes the feed but also again starts to open it. It is as if the feed data has been written twice to the same file. You say that if you manually regenerate the feed it is ok again. Does that mean that the failure only occurs when you regenerate the feed in auto mode?
Hi Michel, good insight looking at the raw xml strange. Mmm strange. It only happens indeed with the auto mode. Not on the manual regenerate. But then again: it happens not always. I have 4 feeds of 3 products. This morning only one was “corrupt”. I use your plugin on a lot of shops, also the premium plugin. I have not seen this issue before. But this shop is also hosted on another server (not mine or in my control) and with other caching plugins then i’m used too. I’m thinking it should have something to do with caching. There are 2 plugins: Litespeed and Super Page Cache (for Cloudflare). So, i’m going to do some more tests. I keep you informed.
Dave, strange indeed. Can you confirm you’re using the latest version on that specific shop?
Yes, Version 2.23.6
Hi @davelo , Can you try the following: Open the Feed Manager -> Settings page and activate the “Feed process logger” option Then wait for a feed to fail. Once one has failed, do not (yet) regenerate it. Instead: Open the wp-content/uploads/wppfm-logs folder on your server Make a copy of all the log files in that folder and send them to michel (at) wpmarketingrobot.com, refering to this topic. Once you’ve done that you can manually regenerate the feed again. Once I have the logging files I could try to identify the possible cause and might be able to harden the auto feed update process.
Hi Dave, Did you get my previous reply?
Hi Michel, Yes, i was waiting on your reply. 🙂 I sended the logs on 20 june. I’ll send them now again.
Hi Dave, I’m not receiving the mails. Might be that my mail service is blocking the extentions of the files you send. Could you send me an email without files so I can reply to you with another suggestion on how to transfre the files?
Hi Dave, I still haven’t received your mail. I don’t know why your mails are not coming through, but lets try a different approach. Can you please open a ticket here: https://www.wpmarketingrobot.com/support/ and let me know when you entered it so I can assign it to myself?
Hi Dave, I received the files now. Thanks! I will have a look at them just to see if there is an issue I can identify an improve on. I will let you know.
Hi Dave, Thanks for sending the logs. Unfortunately, they indicate that the feed generation is working correctly. The issue is that each feed regeneration overwrites the previous logs, and it appears that a successful regeneration was the most recent logged event. Since you mentioned that the feeds are currently regenerating without problems, I recommend leaving the feed logger enabled until the issue occurs again. If a feed fails, please disable the logger immediately (or make a copy of the log files), then manually regenerate the feeds and send me the updated logs. For now, I will close your ticket. With a bit of luck, this was just a one-time hiccup. Please feel free to reopen the ticket if the issue returns.