Running &resync=1 and then cli seems to work, but..

@romeon hey we’ve been emailing privately – but now I’m going to say something out to the public to spark some interest and find the solution as a team.

When using a caching plugin, you’re getting the benefit of speedy pages which is great, but you have to be careful what you’re turning off as well when you do this. I saw that this plugin had a “cache the REST API responses” and that would be preventing you from seeing the actual syncing progress in our plugin. It was in fact working, but the overview screen was receiving a “cached REST API response” and so the numbers don’t appear to be changing.

We know that using a cache is a very good idea for the right use cases, but we also need to pay attention to the details so that vital processes are going to work as expected. Maybe what needs to happen is to add an exclusion rule, or to possibly disable various aspects of the caching engine to make the core processes work again.

So @romeon the reason you’re probably having such a delay on the order processing was due to this cache. It’s obvious when you do a page refresh – you’ll briefly see the “true count” but then it goes back to the cached count right away due to this problem. Anyway – I’m going to say that your order sync should finish today – but you’ll also need to adjust this caching engine to make sure it’s not impacting the Action Scheduler, or our plugin functionality. Maybe reach out directly to the guys at LightSpeed for some recommendations?

sorry a follow up to this – if you’re using the LightSpeed Cache plugin:

On the tab: Excludes
There is a slot for: Do Not Cache URIs
Which needs to have a value of: /wp-json/mailchimp-for-woocommerce

@romeon I just looked into your account and it looks like you’re all synced up as of now. Thanks for working through things with us. We most certainly found some issues with the cache plugin you were using Lightspeed Cache – we’ve got this in development to try to see if there’s any way we can support it in a future version. I’ll keep you up to date on that but for right now you’re good to go.

If you would please take a moment to leave our plugin a fair review that would be much appreciated ??

@ryanhungate Thank you for the personal support and all you’ve done. As you stated, some weird thing is going on. First I toggled LiteSpeed off, nothing happened. Appearently it leaves caching-stuff in the .htaccess. I had to actually deactivate the liteSpeed plugin before it started running again. Why it’s affecting the scheduler is a big weirdo.

Anyway, all solved, I need to talk with the LS guys to see what’s happening.

@romeon thanks for reporting back. We’ve actually decided to try and debug this ourselves in a staging environment to see if there was anything we could do with folks using this plugin. There’s no guarantee on a time yet but just know that we’re trying to support it if we can. Overall that plugin seems to be doing a lot of good things for the site, but you have to also be really careful about what you’re caching and for how long etc.

If we do find a way to run alongside this plugin we will certainly report back.

Thanks for working through things too. Much appreciated. If you could please take a moment to leave our plugin a fair review that would be very much appreciated!