Sync issues

@adamhomebase does the transient manager plugin allow you to delete the value manually – or does it only look for expired transients? The reason I ask is because this particular problem seems to be that a transient was set to never expire. If so – just delete that one manually.

The ‘regular schedule’ question has 2 answers.

1. if you’re running the WP-CLI version where you’re running wp queue listen – then yes – you need to have either a cron schedule running to assure the process is working.

2. If you’re NOT running the WP-CLI version ( which is the default setup ) you do not have to use a cron schedule – but you should have something that’s triggering traffic to the site like an uptime check every minute or so. The reason for this is because the queue doesn’t have power to process jobs unless the site triggers this process by typical web traffic. Even you just refreshing the page a couple of times should get it to work.

Do you see any syncing going on at all – or is it just logging something like “Sync Started” with nothing else?

I’ll be glad to get you to where you need to be – let’s start with these questions first if you can.

Thanks for the help Ryan.

The transient manager plugin shows all transients. It shows a http_worker_lock transient but its expiration is 1 minute so I didn’t delete it.

After the manual sync it shows no syncing activity at all. The “last updated” date and time is when I manually synced it 5 days ago after reinstalling the plugin.

I’m running the standard non WP-CLI version. If I used the WP-CLI version and triggered the syncing with cron could that solve my issue?

Mailchimp support has recommended I use my test site with the default theme and slowly reactivate plugins to troubleshoot a theme or plugin conflict which I am going to do today.