When the cron/batch option is enabled, you can't rely on the mailchimp api to return the correct subscribe status.
For example when somebody subscribes on the website (and its subscription is queued) and then unsubscribes (before the queue has run), the unsubscribe will not be queued as the user has not yet been subscribed (if you query the mailchimp api directly).
If the cron/batch option is enabled we should never use the mailchimp api directly (except during the queue handling).
This is possible since we store the subscribe status ( #2903853: MailchimpListsSubscription doesnt save 'subscribed' in DB → ).
Closed: won't fix
1.0
API
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Thanks for submitting this ticket — and sorry we didn’t get back to you about it sooner. We are cleaning up old issues and issue for old versions and are going to close this one. If this issue is still relevant for you, please re-open it and update the “Version” field, and include any updates to the behavior you are seeing.With a smaller issue queue, we’ll have an easier time getting back to you.