ryanhungate

@emeove have you “deleted” or just “deactivated” the plugin? I’m wondering if that had anything to do with this. Can you try deleting it and let us know if they still happen?

Great to hear – that’s a new one but I’m glad you said something because this could be a reason as to why other folks have a problem sometimes. We’ll have to put this one in the back pocket to double check too ??

If you feel the plugin has lived up to the standards you expect please feel free to leave a review so it helps others too!

@jami23 just to clarify, when you say “subscriptions”, are you referring to the Mailchimp subscriptions of the users, or are you referring to a “subscription plugin” that you’re using? I’m reading this as you’re asking about the Mailchimp subscriptions.

If this is correct, and by looking at your action scheduler logs, it would seem as if you have a problem with the “scheduled actions” actually running. Do you know if you have WPCRON enabled on this server? Is there anything preventing your scheduled actions from running?

You may need to talk with your host because this reads as if nothing is being processed after being “added to the queue”.

Can you please check into your FATAL logs to see if anything stands out as a problem related to this?

Can you also please have your host validate that your action scheduler is actually able to process items in the queue?

@emeove this is very odd and has never been picked up in any testing or QA on our end. Where exactly are you seeing these empty products? Do you have an example to show? Is this on your actual website, or in Mailchimp?

There’s nothing that would be causing the creation of a product in your store in our plugin code but it could be a combination of “events” firing with other plugins that might be doing something wonky…

If you don’t want to enable the plugin and activate the remote support, we can’t really see anything going on with your site, but rest assured we will help you get to the bottom of this the best we can.

@veniro if you’re trying to sync over a custom field to Mailchimp, that can be done using our custom hooks. This wiki page in particular can be used when an order is being submitted. If you have this custom field you can access this information and return it as a merge field.

@technicalx do you happen to have the full stack trace there as to where it triggers from this job class? I’m sure we can figure out a way to at a minimum, patch this for you while we wait for the next release. Be glad to help.

@wesb2023 by chance are you using caches that might be impacting the rest API routes? If so would you so kindly add an exclusion for anything coming to our plugin? mailchimp-for-woocommerce can be used with a wildcard.

ok great @wesb2023 – things look like they’re syncing right now, so once that’s done we’ll make sure your webhooks are enabled. We will keep an eye on your status in our support tool so please don’t disable that just yet ??

@wesb2023 These hooks are now “invalid” so it’s not a big deal, but for the record please don’t post the full URL’s here because that has your auth token in there… the issue is coming from too many webhooks that are connected to your list. This happens when deleting and re-adding the plugin.

The best thing you can do here is to delete all the hooks that are associated with your list while logged into your Mailchimp account. This should be really easy to do and then the post requests will stop coming over.

The other thing to note, is that this is designed to keep things in sync, so if possible, if you could delete all those hooks, and then enable the “support” option in the plugin, we will be able to turn this back on for you on 1 webhook, not too many like you’re seeing right now.

Let us know if you have any other questions at all about this.

@pizzapie79 we have documentation on our WIKI page here that can help with any custom tags. There’s also a few other examples in this wiki to update merge tags and other customization options to the way we push data to Mailchimp. Let us know if you have any other questions about that!

@alijens ok this is fantastic info. This means there’s a recursion happening on an order update. The way this happens is woocommerce_update_order actions are being fired and continues to fire over and over and over until it runs out of memory or fails. I’m not 100% sure how to solve this off hand yet but that’s the issue. Something is updating the order too much and it’s firing until the process shuts down.

If we think of something we will report back here.

@alijens yeah there’s very little chance a single order will be using up that entire 8GB memory… but what does happen a lot of times is the usage of all things happening at the same time can sometimes trigger that type of thing to happen.

I really don’t know off hand why you’re experiencing that. If it works for “2 items on an order” it should in theory work for 50 items. I also wonder if you have any other plugins that might be trying to update stuff on the fly, causing a recursion loop of jobs being queued or something.

Do you happen to see anything in the Mailchimp log file that shows at the time of you viewing the large orders that it tries to ship things off to the queue right at that moment?

I would open up a separate tab for the Mailchimp plugin logs while you try to view those orders and see what happens right after viewing the order on that log file tab. Maybe there’s a clue here that might show the traces we need to help further. Also I would change the log setting to DEBUG in our plugin to get all logs.

@alijens this one has us scratching our heads pretty good. These problems are very difficult to track from our end. If everything is fine on smaller orders, then it must be related to a rendering of the products in the order. These are where the foreach loops can get a little messy with resource consumption. If you’re getting the 503, that’s a sign of things not being optimized enough and running either out of time, or just consuming too much on the resource side. It shows you’re running out of memory, and the only way around this is to increase that on the server.

Have you tried upping any resources at all to allow for this? What was the most you’ve tried to increase that to? Could it also be related to a PHP INI setting for max memory per process? You actually might need to add a custom code snippet on your orders scripts that will temporarily increase that php max memory setting to see if that works. Have you been able to troubleshoot anything along those lines with your host?

@mouindi the fact your plugin is syncing the same number of contacts / orders makes me instantly think that it has something to do with the way your site might have been migrated to the new WooCommerce High Performance storage. Are you saying that when you view your customers screen, you see 3,000 customers? Or do you have 3,000 “users” in your system?

We’re trying to wrap our heads around this right now but it’s a little hard to do being outside of your server. We’ll be glad to help out of course, just need to know a little more info to do that.

@michaelparak I may have missed your comment about running the curl command – assuming you did exactly what I was asking… but did you use the right Mailchimp API token in the request?