Default Variations not working properly

The filter does not matter as the plugin will retrieve all products for your other feeds too but will just filter some out and not put them in the feed. In fact, adding filters to a feed configuration makes processing harder in terms of server resources.

Can you share the WooCommerce fatal error logs of today and yesterday with us?
This is where you can find those logs: https://docs.woocommerce.com/document/finding-php-error-logs/

Yes of course.

here it is:

2021-02-24T08:13:33+00:00 CRITICAL Uncaught Error: Call to a member function get_available_variations() on bool in /kunder/fshome_6265/fsphph_8909/public/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php:3621
Stack trace:
#0 /kunder/fshome_6265/fsphph_8909/public/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(4470): WooSEA_Get_Products->woosea_get_products()
#1 /kunder/fshome_6265/fsphph_8909/public/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(2068): woosea_continue_batch()
#2 /kunder/fshome_6265/fsphph_8909/public/wp-includes/class-wp-hook.php(287): woosea_project_refresh()
#3 /kunder/fshome_6265/fsphph_8909/public/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#4 /kunder/fshome_6265/fsphph_8909/public/wp-includes/plugin.php(484): WP_Hook->do_action()
#5 /kunder/fshome_6265/fsphph_8909/public/wp-admin/admin-ajax.php(184): do_action()
#6 {main}
  thrown in /kunder/fshome_6265/fsphph_8909/public/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php on line 3621

2021-02-24T08:29:52+00:00 CRITICAL Uncaught Error: Call to a member function get_available_variations() on bool in /kunder/fshome_6265/fsphph_8909/public/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php:3621
Stack trace:
#0 /kunder/fshome_6265/fsphph_8909/public/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(4470): WooSEA_Get_Products->woosea_get_products()
#1 /kunder/fshome_6265/fsphph_8909/public/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(2068): woosea_continue_batch()
#2 /kunder/fshome_6265/fsphph_8909/public/wp-includes/class-wp-hook.php(287): woosea_project_refresh()
#3 /kunder/fshome_6265/fsphph_8909/public/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#4 /kunder/fshome_6265/fsphph_8909/public/wp-includes/plugin.php(484): WP_Hook->do_action()
#5 /kunder/fshome_6265/fsphph_8909/public/wp-admin/admin-ajax.php(184): do_action()
#6 {main}
  thrown in /kunder/fshome_6265/fsphph_8909/public/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php on line 3621

Thanks fir this. Based on the error you are getting it seems you are not on the most recent version of the plugin. Can you make sure to update to version 9.7.6 of our plugin. Changes are that that will already solve the issue at hand.

https://prnt.sc/10gy7iw

this is the version I am using.

I see, the error message you pasted is not from today or yesterday. It is from the 24th of February. Can you please share the error logs of today and yesterday?

The last fatal error I got is:

2021-03-06T18:23:14+00:00 CRITICAL Allowed memory size of 536870912 bytes exhausted (tried to allocate 655360 bytes) in /kunder/fshome_6265/fsphph_8909/public/wp-includes/class-wp-object-cache.php on line 446

I don’t have from Yesterday or Today.

When you stop processing of the feed and then do a manual refresh of the feed again then changes are that an error log for today also will be created as I suspect your feed is getting stuck processing because of the error you pasted above. Your website runs out of memory when processing the feed.

Can you increase the allowed maximum memory usage of your website?

Ok I will check it with my server.

But why it happens only at this feed and not at the other feeds that are harder to proccess?

And actually it happened after an update of your plugin (can’t remember which version).
Before that version it worked fine.

My server’s memory limit is at 512MB.

Yes some feeds are harder to process then others, especially the Skroutz one is a disaster because of their strange feed requirements so I am not surprised at all that it takes more memory.

Did you test this already?

When you stop processing of the feed and then do a manual refresh of the feed again then changes are that an error log for today also will be created as I suspect your feed is getting stuck processing because of the error you pasted above.

It seems that is caused of Skroutz specific requirements.

Because I create the same feed with same choices enabled and filters/rules for Google shopping and it worked fine.

So I have to increase my memory limit from the server.

We increased memory from 512 to 768 but it didn’t work out.

Also I don’t have any fatal error from last 4 days.

This stuck happened about ~1-2 weeks ago after an update from your plugin about Skroutz I think..

As I remeber about 2 weeks ago, the feed wasa broken because of an error.

And after the update it never processed to 100% again.

Did you already try creating a complete new feed for Skroutz? Does it get stuck too and does it create fatal error logs?

I just hit the refresh button for a Skroutz feed, then hit refresh of the page to see if it started proccessing and this happened: https://prnt.sc/10hyt4r