Constant Contact wants to help you succeed! We’re celebrating our professional service programs on the Constant Contact Community this month and you have a chance to try one of the services for free! Learn more.
We recently published an update on this in our last set of release notes in our TechBlog (http://techblog.constantcontact.com). We are hopeful to have a full fix for this out in the next week or so. You'll see updated release notes there when we get the fix to production.
I have a client getting this error (slightly different from OP) when doing bulk upload of contacts:
com.roving.RovingServerException: Undexpected ContactServiceBadResponseException in ContactsAPIServicelmpl.processBadResponseEntity. User Data:
We are using the v1 API. They may be on the new version of the web. Is this error related, or is this something completely different? Has a fix been implemented yet?
We are experiencing the same error: Received unhandled error from CC
com.roving.RovingServerException: Unexpected ContactServiceBadResponseException in ContactsAPIServiceImpl.processBadResponseEntity. User Data:
Do you have an expected date when this fix will be ran? We are at a stand still until this is fixed.
All of these issues, if you're getting that error message, are related to our new Contact Management platform. Internally, our API relies on a bulk import service which was designed for our old Contact Management system. When we migrate an account to our new Contact Management platform, we occasionally are seeing performance issues which cause the imports to fail. In full transparency, we're seeing a just under 1% error rate on imports.
We have been working hard to rewrite our entire batch processing service for imports. We believe we are about 2-4 weeks from finishing that and rolling it out to resolve this issue for 100% of our developers. Our initial performance testing has showed an over 600% increase in performance as well as 0% error rates.
I know the 2-4 week timeline is very frustrating for accounts which are seeing failed imports. We are trying to be very careful in rolling this out as we don't want to make the problem worse than the current one is. For a good portion of our customers using the API, this is either a sporadic issue or a non-issue. We don't want to roll out a fixt that isn't ready and increase that error rate from >1% to something larger. We will post information as soon as we roll this fix out to production and confirm that it is both stable and resolves all these issues.
Thanks again for your patience and continued reporting of the issue. We use the level of reporting we get to gauge priority like any software company and this has helped us to raise this up and get a solution moving quicker by getting this level of reporting.
Thanks for the update. Does this affect importing contacts into Constant Contact using a CSV file? Our work around is importing contacts using a CSV file. A large number of the contacts in the file are not added in Constant Contact.The file has all of the required information. Is anyone else experiencing this problem that has RovingServerException error? Thanks.
This issue only impacts imports through the API. If your customers import through our UI, they should see no issues. As mentioned earlier, the majority of API imports don't see any issues either with the error rate we're seeing being >1% now. We are in the process of finishing up our last tests on our new rewrite of our import tools and we expect to have those rolled out to production in 2-4 weeks depending on final testing. This should completely eliminate any of these issues you're seeing.
Our own account is now experiencing this issue.
So when this fix is released, will it be contained in the v1 API code, or will it be all on your end? Will we have to do any rewrites of our integration, or will all of our existing code continue to function?
Fix is completely contained in our backend and will be transparent to developers. Shouldn't have to make any changes.