- Issue created by @Anybody
- Status changed to Closed: works as designed
2 months ago 7:59pm 11 September 2024 - 🇺🇸United States xenophyle
Based on a web search of this phrase, this is an issue on the Mailchimp end of things and isn't related to the module.
- 🇩🇪Germany Anybody Porta Westfalica
@xenophyle I don't really agree. The API was used via the module and we did nothing special. Maybe the module simply sends too many requests and should better combine them in a timeframe or something like that?
I'd vote to reopen this.
- 🇺🇸United States bdimaggio Boston, MA
Hey there — this is a tricky one. We have seen it a couple of times (well, once → that I know of) over the years we've been maintaining the Mailchimp suite, but we've never successfully pinned down what causes it. I am encouraged that it has only made it to the issue queue that one time, but of course I'm sure that's no consolation for you.
To try and make more progress with it, let's get all the info we can.
- Can you paste here the entire error message you're seeing (including all HTML)?
- Did the problem definitively start at a certain point (e.g. after upgrading to a certain version of the module)?
- If you're not already using OAuth rather than an API key to authenticate, can you try that (admittedly, a shot in the dark)?