This repository has been archived by the owner on Mar 24, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 119
SerializationException when MailChimp returns error page instead of an API result #155
Comments
This is a great point. It'd be nice if we could get an easily reproducible case. The next time this happens, can you see if it's dropping into this exception handler here? If it is, we could probably add another check to see if it's a JSON based response or not. First 'n' characters of the page body might be a bit interesting to pull out (do you have an HTML parser in mind for that?) |
Yes, it looks like that's where we end up. Here's my stack trace:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In some cases (and I haven't been able to determine when this happens) MailChimp returns an error page instead of an API response - html instead of json. Possibly when the service is down?
MailChimpManager throws SerializationException when this happens.
It would be nicer to get a MailChimpAPIException of some kind, ideally including the first n characters of the page body.
This is the exception we get:
The text was updated successfully, but these errors were encountered: