Open katekleiman opened 6 years ago
Also seeing some issues like this and things not seeming to sync civi > mailchimp properly, not sure if related.
Have you enabled debugging and looked at the logs of a sync?
If you run a sync and find the response_body_url amazonaws URL from the log you can download the JSON response from mailchimp (have to do it quickly or the file expires on the server) which contains the error codes. In my case I'm getting a lot of errors like this:
{"status_code":400,"operation_id":null,"response":"{\"type\":\"http:\/\/developer.mailchimp.com\/documentation\/mailchimp\/guides\/error-glossary\/\",\"title\":\"Invalid Resource\",\"status\":400,\"detail\":\"Invalid interest ID: '57d5ad703b'.\",\"instance\":\"\"}"}
We're seeing a bunch of errors with the push out to Mailchimp. Our list there is divided into segments using Membership Status to define each group. When I sync, results are:
Shouldn't the number in sync already be (1976 + 93)? Some members are in the "grace" segment when they should be in "expired".
Thanks for your help.