Oliver Jusinger
Forum Replies Created
-
@msykes I also want to thank you for your quick help and the release of the new version! Recurring events work now.
Hi @superlemon1998
great, this update works for me, the auto-scheduled jobs now created complete feeds (hourly full creation with default batch-size)
I hope I could help and the reason was not some strange usecase on my side. It looks like processing is slower now, but most important it seems you have managed to fix the problem, thx!- This reply was modified 11 months, 1 week ago by Oliver Jusinger.
- This reply was modified 11 months, 1 week ago by Oliver Jusinger.
I changed the batch-size to 25000 because I don’t trust the batch-handling:
For the scheduled feed generation then I got:Fatal error Maximum execution time of 120 seconds exceeded in /var/www/vhosts/.../httpdocs/wp-content/object-cache.php on line 1990
For manual updates I get:action marked as failed after 300 seconds. Unknown error occurred. Check server, PHP and database error logs to diagnose cause.
So there seem to be different timeouts for scheduled jobs and manual updates – manual updates don’t use the object cache? I am using the plugin “Redis Object Cache” (free version). But the timeout is not the problem:Afterwards I changed the batch-size back to 250 and did a manual update. This works as always.
Scheduled jobs with batch-size 250 (or default) didn’t ever show any errors in the scheduler but the resulting feed nevertheless was always broken.
Is there way to set the time for the next scheduled feed creation, I would really prefer to debug during daytimes (“1 day” is currently at around 2:30 am … )?- This reply was modified 11 months, 1 week ago by Oliver Jusinger.
I am sorry, but the update didn’t work, the feed again only contains 25 products instead of about 10.000. Since g:id is my product id and the feed only contains the first few product ids I think the other scheduled jobs didn’t manage to add their result to the feed.
I watched the scheduled update running, it took as long as a manual update (maybe 5-8 minutes), so it seems the data was processed but not written into the resulting feed?
Not sure if the scheduler information helps – there are always 2 jobs with identical feed_id and offsets, the last jobs didn’t have offsets and were “completed via Async Request” instead of “…heartbeat”:adt_pfp_as_product_feed_update_statsComplete
'feed_id' => 109188
Non-repeating2025-06-18 00:35:40 +0000
(24 minutes 29 seconds ago)- 2025-06-18 00:35:40 +0000
action created - 2025-06-18 00:35:45 +0000
action started via Async Request - 2025-06-18 00:35:45 +0000
action complete via Async Request
adt_pfp_as_product_feed_update_statsComplete
'feed_id' => 109188
Non-repeating2025-06-18 00:35:38 +0000
(24 minutes 31 seconds ago)- 2025-06-18 00:35:37 +0000
action created - 2025-06-18 00:35:39 +0000
action started via Async Request - 2025-06-18 00:35:39 +0000
action complete via Async Request
adt_pfp_as_generate_product_feed_batchComplete
'feed_id' => 109188'offset' => 23750'batch_size' => 250
adt_pfp_as_generate_product_feed_batch_109188Non-repeating2025-06-18 00:35:34 +0000
(24 minutes 35 seconds ago)- 2025-06-18 00:35:33 +0000
action created - 2025-06-18 00:35:38 +0000
action started via Product Feed: heartbeat - 2025-06-18 00:35:40 +0000
action complete via Product Feed: heartbeat
adt_pfp_as_generate_product_feed_batchComplete
'feed_id' => 109188'offset' => 23750'batch_size' => 250
adt_pfp_as_generate_product_feed_batch_109188Non-repeating2025-06-18 00:35:34 +0000
(24 minutes 35 seconds ago)- 2025-06-18 00:35:33 +0000
action created - 2025-06-18 00:35:34 +0000
action started via Product Feed: heartbeat - 2025-06-18 00:35:37 +0000
action complete via Product Feed: heartbeat
adt_pfp_as_generate_product_feed_batchComplete
'feed_id' => 109188'offset' => 23500'batch_size' => 250
adt_pfp_as_generate_product_feed_batch_109188Non-repeating2025-06-18 00:35:25 +0000
(24 minutes 44 seconds ago)- 2025-06-18 00:35:24 +0000
action created - 2025-06-18 00:35:29 +0000
action started via Async Request - 2025-06-18 00:35:33 +0000
action complete via Async Request
adt_pfp_as_generate_product_feed_batchComplete
'feed_id' => 109188'offset' => 23500'batch_size' => 250
adt_pfp_as_generate_product_feed_batch_109188Non-repeating2025-06-18 00:35:25 +0000
(24 minutes 44 seconds ago)- 2025-06-18 00:35:24 +0000
action created - 2025-06-18 00:35:25 +0000
action started via Product Feed: heartbeat - 2025-06-18 00:35:33 +0000
action complete via Product Feed: heartbeat
- This reply was modified 11 months, 1 week ago by Oliver Jusinger.
- This reply was modified 11 months, 1 week ago by Oliver Jusinger.
- This reply was modified 11 months, 1 week ago by Oliver Jusinger.
Hi @tanvirh
great, thank you for your support. I have installed the new version and will inform you in about 3-4h if creating the feed with scheduled jobs worked. My PHP memory limit is quite high (768 MB), but maybe it was reached because of too many products.Hi @superlemon1998
thx for your support. Here is my full log: https://cloud.jusinger.at/s/Sjcojfxr885F45o (please ignore the first feed, the second #109188 is relevant)
It seems more and more obvious to me that scheduled jobs overwrite each other so the resulting feed only contains products < batch-size.
I did a manual update (which usually work) while scheduled jobs were still running and it got overwritten. Therefore I can already provide a broken feed and its log which I guess was created by 1 scheduled job (batch-size 250, total products > 23.000, expected result 10.000 products, feed < 100 products).Thx for your quick reply! “Remove products that did not have sales in the last days” is set to “0” (I didn’t touch that, it is the default?)
I just did a manual update to keep the feed working so I can only send you the full log of an auto-update in about 24h.
I don’t think it is related to “Remove products that did not have sales in the last days” because only much fewer products are sold daily than the broken feeds delivers. Scheduled jobs overwriting each other is my guess, it roughly matches with the resulting numbers (batch-size).- This reply was modified 11 months, 2 weeks ago by Oliver Jusinger.
- This reply was modified 11 months, 2 weeks ago by Oliver Jusinger.
Forum: Plugins
In reply to: [FiboSearch - Ajax Search for WooCommerce] Comulative Layout Shift / CLSHi @c0nst
wow, thank you for your incredible support, your solution works perfectly.
Best regards,
OliverForum: Reviews
In reply to: [WPC Smart Wishlist for WooCommerce] Works out of the boxthank you, rating updated 🙂 Unfortunately I am currently away and can provide the informations only in 3 about weeks.
Super, danke dir für die rasche Behebung!
tooltipster.bundle.min.css und tooltipster.bundle.min.js fehlen.
WP-Optimize scheint nicht schuld zu sein 😉
LG Oliver