Constant Contact plugin issues

Would still love to see the logs if/as available, just in case something else stands out. Do you have cron disabled by any chance? just in case that’s playing a part in things.

I do not have cron disabled – but I may have found a solution – by uninstalling and then reinstalling the plugin and setting up the connection while logged into Constant Contact as a different user. After doing this the connection has not dropped as of yet after being up for a day. It was previously disconnecting every night. Someone at Constant Contact support suggested this, saying it had worked for others who had this problem.

Interesting, and not something I have previously heard, regarding changing connected user contributing to more stability. Have things stayed stable over the weekend? Edit: Also are you able/willing to share the email addresses that were being used, we can check on some things with regards to that. I can provide an email address to send those to, if you don’t want to share them publicly This reply was modified 2 weeks, 2 days ago by Michael Beckwith .

Disconnections have resumed again. Two disconnections in the past 24 hours. The latest error message is: API.INFO: A failed API attempt was caught and will be retried after reconnection. I prefer not to share user email addresses, but am doubtful they are relevant. And now apparently the user that retrieved the auth code for the connection doesn’t seem to be the factor causing the connection to drop.

We can definitely check on some things if we know the users being authenticated with. If you could, please send those to wordpresssupport@constantcontact.com The new log line indicates someone submitted to the form, but because of disconnected status, it couldn’t push the whole way through until re-connected. That’ll be automated.

I’m having this same issue. We checked all conflicting plugins, removed one that was likely causing the issue but the plugin keeps disconnecting. I’ve tried asking Constant Contact’s support but they keep referring me here. Has anyone been successful at debugging this to resolve the connectivity issue?

We have unearthed some new leads internally that we’ll be exploring very soon, to hopefully help resolve these inconsistent connection issues that have been nagging for a long time.

I neglected to mention – we are using the latest version -2.19. This issue started happening after upgrading to 2.19 so it could be an issue/bug in this version.

If you wish to revert for the moment, you can find the previous version at https://downloads.wordpress.org/plugin/constant-contact-forms.2.18.0.zip Good detail to note that it happened after the latest.

Disconnections have continued so I have downgraded to version 2.18 to see if it helps.

We’ve been working on changes to the plugin after discovering some cases of what’s known as concurrency/race conditions. Would either of you be willing to try out a version of the plugin with those specific changes to see if things stabilize? This would be ahead of a mass release. If things turn around well, we’d move the same changes to the next plugin release for everyone. Interested?

I would be fine with that. Please note that since I downgraded to 2.18 about 24 hours ago I have not had a disconnection yet. So if it’s of value to have me continue to test that I can. But happy to install this new version.

Thank you for the interest, it’s definitely something we want to get tackled. The biggest change that came with 2.19.0 was around comparing domains, and disconnecting if there’s a mismatch. This is particularly around the idea of say a database was cloned down to a different environment with a different URL away from what we assume would be the “production” or “live” site. So, this version linked at https://www.dropbox.com/scl/fi/xtar5i64n8pfiuu16s919/constant-contact-forms-beta.zip?rlkey=06dvgk0nr7tkx8wmc3cz1n9cp&dl=0 is based on 2.19.0, and the version numbers are going to reflect that, but the name of the plugin in the listing should have “BETA” mentioned in it. Biggest changes in this copy is the removal of WP Cron integration as a whole since over time, we added more real-time refresh checks, and thus the potential race conditions I mentioned yesterday. Perhaps hold until you potentially get a new disconnect before trying it out though, if things have seemed to manage to stabilize.

Since 2.18 has been stable for a couple of days I went ahead and upgraded to your 2.19 beta version. I did not uninstall and re-setup the plugin – just upgraded directly to this version. If it matters and you’d prefer I uninstall and do a fresh install of this beta version let me know. Otherwise I will let it run as is and let you know if it disconnects.

Direct upgrade should be just fine, without uninstall/reinstall. Here’s to hoping things stay considerably more stable and self managing.

Hi all, I’ve been experiencing regular disconnections too, ever since my site was upgraded to WordPress v7.0, running on PHP 8.1. I’ve Constant Contact Version 2.19 installed. A few times after copying and pasting a new CC key, I kept getting the WordPress critical error screen. I turned on debug mode in wp-config to write to the debug.log file and noticed the following: PHP Warning: Undefined array key “contact_id” in /wp-content/plugins/constant-contact-forms/includes/class-api.php on line 926 PHP Fatal error: Uncaught TypeError: ConstantContact_Client::get_contact(): Argument #1 ($contact_id) must be of type string, null given, called in /wp-content/plugins/constant-contact-forms/includes/class-api.php on line 926 and defined in /wp-content/plugins/constant-contact-forms/includes/class-client.php:89 Not sure if this is relevant but it might help shed some light on the disconnections issue. I cleared the ctct_missed_api_requests row in the wp_options table to prevent the critical issue. However the disconnections still continue. If you can continue to look this that would be great, thanks.

@eddie8181 Biggest change to keep an eye on would be details in my comment at https://wordpress.org/support/topic/constant-contact-plugin-issues/#post-18934483 which is all new for this week. Regarding the error you experienced, it seems that an API POST request failed to either create or update a submitted contact. May or may not be related to API access details, but an error I see we should be able to prevent from occurring as well, so adding an internal ticket to help prevent that.

@eddie8181 do you have a timestamp for that error? also what account is connected for it? That error is a bit of a potential odd/rare one and we’re wanting to double check on some things on the API end. Thanks.

Hi Michael, thanks for the quick response. Sure, so here are the entries from from the plugin log. The plugin disconnected a few days beforehand, so I manually reconnected it at 2026-6-09, 08:33. [2026-6-07, 19:07] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] [] [2026-6-08, 21:37] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] [] [2026-6-09, 08:33] Refresh Token:.INFO: Refresh token triggered [] [] [2026-6-09, 08:33] Refresh Token: .INFO: Old Refresh Token: e9pVMVK5*** [] [] [2026-6-09, 08:33] Access Token: .INFO: Old Access Token: eyJraWQi*** [] [] [2026-6-09, 08:33] Refresh Token: .INFO: Refresh token successfully received [] [] [2026-6-09, 08:33] Refresh Token: .INFO: New Refresh Token: _hSGQNlD*** [] [] [2026-6-09, 08:33] Access Token: .INFO: New Access Token: eyJraWQi*** [] [] [2026-6-09, 08:33] Expiration time:.INFO: Current time: 2026-6-09, 09:33 Estimated expiration time: 2026-6-10, 09:33 [] [] As soon as I did that, I got the PHP errors I mentioned above in the backend, both timestamped [09-Jun-2026 08:33:43 UTC] in the WordPress logs. I’ll email my CC account details to you at the wordpresssupport@constantcontact.com email address. Thanks

Confirming received the email reachout.

The beta version plugin disconnected after being up about a day and a half. So I am downgrading again to 2.18. If there is another beta you’d like me to try I am happy to. I will let you know if 2.18 stays connected.

Hi @jmoss66 Can you provide the latest logs for the plugin? We have one other person who’s had theirs going for a few days now and still going strong by the looks of it, so that’s definitely sounding promising overall.

Here is the latest log. It disconnected Friday evening and I haven’t been able to reconnect yet because I’m waiting for the login code from the account owner [2026-6-09, 13:35] API.INFO: Submitted contact data ["Extra information",[{"first_name___67281f13970cdb5004f661a71a14ad20":{"key":"first_name","val":"Lizzy"},"last_name___71c1b9c0961e0f7a4174c373329e6d5f":{"key":"last_name","val":"Simmons"},"email___30c05bd7fc699437454c374fa5b9eacb":{"key":"email","val":" @gmail.com"},"email":" @gmail.com","lists___d3b0bce7b8f8412a9b0c9f973bd87a30":{"key":"lists","val":""},"list":["8f184da0-1b38-11e3-800c-d4ae52844390"],"anniversary":{"key":"anniversary","val":""}}]] [] [2026-6-10, 12:10] Refresh Token:.INFO: Refresh token triggered [] [] [2026-6-10, 12:11] Refresh Token: .INFO: Old Refresh Token: lSQwrgw6 * [] [] [2026-6-10, 12:11] Access Token: .INFO: Old Access Token: eyJraWQi * [] [] [2026-6-10, 12:11] Refresh Token: .INFO: Refresh token successfully received [] [] [2026-6-10, 12:11] Refresh Token: .INFO: New Refresh Token: Qvu7qJM_ * [] [] [2026-6-10, 12:11] Access Token: .INFO: New Access Token: eyJraWQi * [] [] [2026-6-10, 12:11] Expiration time:.INFO: Current time: 2026-6-10, 06:11 Estimated expiration time: 2026-6-11, 06:11 [] [] [2026-6-10, 20:31] API.INFO: Submitted contact data ["Extra information",[{"first_name___67281f13970cdb5004f661a71a14ad20":{"key":"first_name","val":"DennisCem"},"last_name___71c1b9c0961e0f7a4174c373329e6d5f":{"key":"last_name","val":"DennisCem"},"email___30c05bd7fc699437454c374fa5b9eacb":{"key":"email","val":" @web.de"},"email":" @web.de","lists___d3b0bce7b8f8412a9b0c9f973bd87a30":{"key":"lists","val":""},"recaptcha-v3-token":{"key":"recaptcha-v3-token","val":"0cAFcWeA4L102nYsEDd27I4jim7_9R_lqETYJbnzHfnH6s7X0fbsrRZpeNeEEIXFm7pvt0-jGqXC2N6DvBLR3eG1dRwkHjSirvtNFfR09dKTo5t6899PJjT4yYsDHMa8MosB0bs3HkwTLzv2ejGluYP-6XhNj1F41p-KPMv4qtRlQoSSs2MuP-qdIe3BiJC_L7kM2JNnOaz_YoK6a5YouAIMXmBQHqYp9YVZSsnJ60b3Wz9t2WsuDykBr4BBrYZ7qZbYxYItAo4475YMIad70ObpVtCAcdu3pVOsHrQhKNXRyZs9sN_9D7OKyiMqWbOeyMPK7rtxafJWj18ZI_E9EeLeWHHw3LdgeMj5qNfYkW0_7K4JZRMulhtjtF4PY-zTsEhiuf_TXMm-R_MRRF27IYx7D1xVBzeT9AwzF7Z5ms-voU4uP4CoNmWp-N-LkxPVyrB4BRoli-GTGkyentgSDmjY21fTkGGr60nSxGJ1NtKqyUYljNgbfk7tFU7eAsixcNeFrNhlNJbyRQQ23DXC9c_aBRmsBGk0mNMmLnrTqrMyI9tdIq9B3Gu-4jrGRRSpJGRqKFLFMPrtPjMubliDzk4yYxhD3JvewDu7z3Nfix0MHA5ddy27RUAsRAdg4ckMQvbV4oYK0KDa9nRkapiBzYBSvo7cXQMHAAbdvo6ymmgnI13WAZs5xHwJeLxhCNcxjvCtbusO4IZKugzbv85llxfc6lJtVr-dWWaTgfnGUNth0uC5Ob6Hri9cadJ1NTlCO3CScQXBWDVHhsWnXk0aTJH5LO5mdemrkONaqxowVgR_grhl3eSfOfwq5_laooD-RxoWrSbf4FTLgLBX-zjAPlagjASuXajrSu1IWuW6lSNIEj0_qPYwpadWjdoXr4N1PHaWPxbt7YL0KOjw62v-6QIZAlRhBAAgIn8vNKLyRjpx9iFSt7bBGiNOTtJj8nHGRrVLxDAIboDKId77CyyNSsbmMXqfNMxCfKKm64yXdTfGnYDZ21KagHg0gmmr-qtnQank7DMGhnmyBO3J4IB9XaLGwVX5uBHM0VIqA3kaanJh9GmmzWraGiG0uVM7nBTZLv3EtAs8vf6tU6o0LjfMhQ7AqEnlMyiBltLW6F0IxD6YVJN9Z_63wH-rbXoex0fT8qZyqVjEQ0dtlCSorZZqAG-RnwVvoKu6Mnl8KMe0jiDqyRIO6-WIKJYD2W7G980VC9NIQcHMv7HFNXBm5ry_-6BGA1JeIPOglhiz9JHbjEy_q9yvRObBwycy3aUES4BnWKWK...

Thanks. From the expiration line to the “A failed API attempt…” line has me feeling like we’re not reaching some spots, which is for us to review.

Michael, Would you prefer for me to continue running the 2.19 beta or revert to 2.18?

For the sake of some more thorough testing/confirmation hopes, the beta would be preferred. Especially with the only changes involved with it is largely removal of WP Cron integration that was contributing to the race conditions

Ok, I’ve got the beta running and will let you know if it disconnects again

Appreciate the willingness to help here.

After one day and 21 hours it disconnected again.

Able to provide the current logs from the last few days?

I have emailed it to wordpresssupport@constantcontact.com

Confirmed receiving, thank you for that.

Another disconnect a few hours after the last one. Debug log has no additional information than the one sent earlier.

Noted and received the newest logs. Seeing this proverbial “hole” in timeline, where we have this [2026-6-16, 17:15] – successful refresh, estimated expiration of 2026-6-17 17:15 [2026-6-17, 04:13] – successful signup [2026-6-18, 03:03] – failed attempt Definitely curious if and likely why not, a refresh attempt wasn’t made after 2026-6-17 17:15 Thinking and reviewing.

Hi Michael, We have been having disconnect issues also and I went ahead and installed the 2.19.0 beta version and got our first disconnect again the two days later and another one today. Would love to see this fixed. thanks for your efforts

@ndenaant I definitely want this figured out and diagnosed and determined as well, possibly more than anyone realizes. That said, if you haven’t yet, it’s worth applying the 2.20.0 release that was pushed out yesterday. It has the beta changes as well as other changes that was added in a less publicized “beta 2” that was iterated on with someone via private correspondence. 2.20.0 also has much more logging added, which is intended to get a stronger breadcrumb trail for us.

Thank you Michael. I didn’t check if a newer version was available but just installed it, fingers crossed 😉