svaldesm

Hi Eva,

The refresh interval is daily and I haven’t changed the batch size.
Unfortunately the logs don’t say much about the issue.

Hi Eva,

Sorry for not answering, I never got to see this response.
Actually, the problem has not been resolved.

For a few days, it worked fine. I deleted the feed and created a new one from scratch with good results. Anything else on the store works just fine.

A few days ago, again I was getting zero results without doing any significant change on my store. We have 56,000 products (and keep publishing about 400/day) and only 30,000 on stock, not sure if that affects. I increased max memory and timeout in case it was that. The feed has a filter for removing out of stock products.

After a few refreshes, it worked fine. But then, it started behaving strange again. Look at this graph:

Graph

Not sure how to proceed. There are over 6,000 products duplicated on the feed. I’ve activated/deactivated, updated feed config, etc. but nothing seems to work.
Do you know how is this possible?

Thanks!

New update:

I tried creating a new feed from scratch. Apparently it worked (so far), but there are still about 2,500 duplicated products (which didn’t happened before).

Any idea on why that is happening?

Thanks!

To give more background:

– I tried removing the old csv in case there was a permission issue. At first, that seemed to work and I downloaded the file, that had over 33,000 products, of which 2,700 were duplicated.
– Then, after a while (say 3min), the feed reseted and now it has only 4 products in it.

Hi Eva,

After turning the plugin off/on, the crons did activate again.
But when the feed was suppose to update, it never did and now the crons for the plugin are gone.
Any idea on how to debug this?
WP-Cron is active, Redis is disabled, we have many visitors so Cron runs all the time.

Thanks,

Hi Eva,

Indeed it rescheduled the crons. I’ll wait a few days with the feed without being updated to see if it’s the feed or something else that breaks the cancel_unpaid_orders cron.
In case nothing else breaks it, I’ll turn on again automatic updates of the feed and check if that is the cause of the issue.

Thanks a lot for your help and I’ll keep you posted to further diagnosis.

Hi Eva,

I’m sorry, I wrote that wrong. Redis is disabled on this site.

So I’m not sure how to debug the behavior of the plugin and why it breaks.
A yellow flag (maybe) is that according to the config of the plugin, WP-Cron is disabled. Not sure why that happens, because we can even see Cron Events with WP Crontrol (otherwise impossible if the plugin would be disabled).

If you know ways to debug or what to look for in the logs, that would be very helpful (are there any logs in the plugin?)

Thanks a lot,

Hi Eva,

It does make sense and it’s clear to me for point 1.

What I’m not very clear is on point 2. As I wrote above, when the plugin runs “automatically” it somehow breaks other cron tasks. Could it be that RAM usage or something with server configuration makes it crash? Because the feed does not get updated. Please mind this is a very big machine and it handles lots of traffic perfectly, so it’s not a hardware issue (but maybe a config one).

How can we debug this further? Is there any known config (php memory, RAM, etc.) that makes the plugin “crash” when automatically updating? It somehow conflicts with something else apparently.
WP-Cron is enabled and Redis as well on this server and the feed is refreshed when manually done.

Thanks for your help,

Hi,

Apparently this is related to a feed plugin that somehow “hangs” the server. We are still investigating, but it’s non-related to WC.

Thanks for your answer.

Hi Eva,

Thanks for your answer. There are two topics here that I would like to discuss:

1. Using server cron instead of WP-Cron: we’ve been advised many times to use server cron for several benefits regarding server performance. If adjusting server time to, say, 1 or 2 minutes, will this still work? Could you please elaborate more on how the plugin works in creating batches?

2. Plugin breaking some crons functionality and doesn’t update: when we manually update the plugin, it works. But the scheduled updates don’t work (Redis is not working on this server).
In fact, what’s even worse is that somehow other cron schedules suffer because of this, probably because something happens with this task that gets hanged.
For example woocommerce_cancel_unpaid_orders only gets scheduled after the last execution ends. It does run but at the same time that the feed should be updated, something happens and it doesn’t work more.
We have turned the feed plugin off and it does seem to work.
This is a 16GB server with regular traffic, it works very fast, so it’s not hardware related. Maybe a config issue might be breaking it, but there’s not much on the logs right now. Any clue on what can this be about?

Thanks a lot!

Hi Eva,

Sorry for the blackout, I was out on vacations.

Unfortunately we need Redis for increasing speed on our site and I’m pretty sure more users will use it as time passes. Object caching is very useful for WP sites, as it caches many of the queries needed. For example, in our case we go from ~450 queries to ~130 just by turning it on and retrieving the info on Redis instead of the database.

I read another topic from about 7 months ago where you were speaking about this. Since then, do you have more information on how this might be fixed? I’ve tried other plugins (like the one from WebAppick) and it worked with Redis fine (we switched for other reasons).
Can you please elaborate more on any workarounds possibles to get this working?

Thanks a lot in advance and I really would like to highlight the great service you have, your answers are generally good, precise and quick. Cheers on that ??

Thanks!

We run the cron manually and there’s nothing wrong with it.
Is the workflow the same if it is triggered manually rather than automatically from the cron?

I see that the cron itself hasn’t been scheduled for updating again. I’ve turned on/off the plugin, on/off the feed, saved settings and nothings make it schedule.

Another thing weird is that, on the plugin Settings page, it says the WP-Cron is disabled, but I know it’s enabled on WP-Config and other cron schedules are working.

Any known issue with this as well?

Thanks

Santiago

• This reply was modified 5 years, 6 months ago by svaldesm.

Hi Eva, thanks for your quick answer.

How much products can this plugin support?
We don’t have variations, so it’s only the products (and it is suppose to filter them by “in stock”, in which case it will only show 26,0000).

We haven’t changed anything beside that. Do you have more customers using your plugin for so many products? Is this made for scalability?

Regarding the error, we are debugging further, but apparently it’s related to the plugin.

Thanks

Hi Eva,

So this means that the plugin won’t work when Redis cache is enabled?
Or it’s just going to work slower?

Thanks

Hi Eva,

Thanks for the update. It would be great to change the time and also the batch size. Maybe you can set a huge warning.

Another unrelated thing I realized is that the plugin doesn’t get along with Redis, is there any known bug or issue?
It was working fine until now.

Thanks a lot,