Connection issue
-
Keep getting this error:
Constant Contact Forms has experienced issues that may need addressed and functionality may be missing. Please enable the “Support” checkbox under the Support tab in Constant Contact settings and start a forum support thread. Our support team will aid with further steps.Dismiss this notice.
Constant Contact Forms has detected errors that indicate a need to manually disconnect and reconnect your Constant Contact account. Visit the Connection Settings to manage.
The page I need help with: [log in to see the link]
-
Are you able to successfully disconnect and then re-authenticate the plugin? Or is taking those steps still resulting in it remaining disconnected?
I have done that many times and its still not removing the disconnection
As it seems to be helping, since I know we clear out connection details on deactivation, can you test and see if deactivating and then re-activating helps clear up this issue? Still investigating the method that things get stuck in this situation, but the clean clearout seems to help get over this proverbial bump.
I have done that many times and it does not change.
And I get this email when someone trys to fill it out. We have detected connection errors for your site, Big Systems. Potentially a failed signup has been detected and will be retried automatically once a new connection has been established. Otherwise, issues with token refreshing have been detected. Please visit your site and perform the steps to reconnect the plugin at your earliest convenience.
Realizing that I didn’t potentially clarify my last comment. My apologies.
I meant deactivate and then reactivate the plugin itself, beyond trying to disconnect and reconnect the Constant Contact account within the settings.
If that’s also what you tried, are you willing and able to test changes for an intended-to-be released bugfix, that we’re trying to confirm consistently fixes the issues? If yes, we’ll be aiming to release to everyone at the start of next week.
still getting this message. Constant Contact Forms has experienced issues that may need addressed and functionality may be missing. Please enable the “Support” checkbox under the Support tab in Constant Contact settings and start a forum support thread. Our support team will aid with further steps.
Im still having the issue
Sorry @marketingbigsys I missed seeing your reply from late last week. My apologies.
Have you applied the released update yet?
Can you visit the settings page for the Constant Contact Forms plugin and enable the support option to reveal our debug log page? Hopefully any logs there can reveal what issues were being experienced.
How do I add the log here? also Have you applied the released update yet? I did not see any update. I am on version 2.16.1.
[2026-2-05, 15:45] API.INFO: ConstantContact_API::get_lists:449 unauthorized: Unauthorized [] [] [2026-2-05, 16:43] API.INFO: Refresh token attempt failed in get_api_token. [] []
[2026-2-06, 18:33] API.INFO: Refresh token attempt failed in get_api_token. [] [] [2026-2-06, 18:33] Cron scheduled: .INFO: yes [] [] [2026-2-06, 18:33] Cron scheduled: .INFO: no [] [] [2026-2-06, 18:33] Cron scheduled: .INFO: no [] [] [2026-2-06, 18:34] Refresh Token:.INFO: Refresh token triggered [] [] [2026-2-06, 18:34] Refresh Token: .INFO: Old Refresh Token: 6Lhnvlvv*** [] [] [2026-2-06, 18:34] Access Token: .INFO: Old Access Token: eyJraWQi*** [] [] [2026-2-06, 18:34] Refresh Token: .INFO: Refresh token successfully received [] [] [2026-2-06, 18:34] Refresh Token: .INFO: New Refresh Token: 3lrZJS8P*** [] [] [2026-2-06, 18:34] Access Token: .INFO: New Access Token: eyJraWQi*** [] [] [2026-2-06, 18:34] Expiration time:.INFO: Current time: 2026-2-06, 12:34 Estimated expiration time: 2026-2-07, 12:34 [] [] [2026-2-07, 17:34] Refresh Token:.INFO: Refresh token triggered [] [] [2026-2-07, 17:34] Refresh Token: .INFO: Old Refresh Token: 3lrZJS8P*** [] [] [2026-2-07, 17:34] Access Token: .INFO: Old Access Token: eyJraWQi*** [] [] [2026-2-07, 17:34] Refresh Token: .INFO: Refresh token successfully received [] [] [2026-2-07, 17:34] Refresh Token: .INFO: New Refresh Token: 3feY7dLf*** [] [] [2026-2-07, 17:34] Access Token: .INFO: New Access Token: eyJraWQi*** [] [] [2026-2-07, 17:34] Expiration time:.INFO: Current time: 2026-2-07, 11:34 Estimated expiration time: 2026-2-08, 11:34 [] [] [2026-2-08, 16:34] Refresh Token:.INFO: Refresh token triggered [] [] [2026-2-08, 16:34] Refresh Token: .INFO: Old Refresh Token: 3feY7dLf*** [] [] [2026-2-08, 16:34] Access Token: .INFO: Old Access Token: eyJraWQi*** [] [] [2026-2-08, 16:34] Refresh Token: .INFO: Refresh token successfully received [] [] [2026-2-08, 16:34] Refresh Token: .INFO: New Refresh Token: LneZqoyB*** [] [] [2026-2-08, 16:34] Access Token: .INFO: New Access Token: eyJraWQi*** [] [] [2026-2-08, 16:34] Expiration time:.INFO: Current time: 2026-2-08, 10:34 Estimated expiration time: 2026-2-09, 10:34 [] [] [2026-2-09, 15:33] Refresh Token:.INFO: Refresh token triggered [] [] [2026-2-09, 15:33] Refresh Token: .INFO: Old Refresh Token: LneZqoyB*** [] [] [2026-2-09, 15:33] Access Token: .INFO: Old Access Token: eyJraWQi*** [] [] [2026-2-09, 15:33] Refresh Token: .INFO: Refresh token successfully received [] [] [2026-2-09, 15:33] Refresh Token: .INFO: New Refresh Token: w3TiDm5o*** [] [] [2026-2-09, 15:33] Access Token: .INFO: New Access Token: eyJraWQi*** [] [] [2026-2-09, 15:33] Expiration time:.INFO: Current time: 2026-2-09, 09:33 Estimated expiration time: 2026-2-10, 09:33 [] [] [2026-2-10, 14:33] Refresh Token:.INFO: Refresh token triggered [] [] [2026-2-10, 14:33] Refresh Token: .INFO: Old Refresh Token: w3TiDm5o*** [] [] [2026-2-10, 14:33] Access Token: .INFO: Old Access Token: eyJraWQi*** [] [] [2026-2-10, 14:33] Refresh Token: .INFO: Refresh token successfully received [] [] [2026-2-10, 14:33] Refresh Token: .INFO: New Refresh Token: kX_ixxsK*** [] [] [2026-2-10, 14:33] Access Token: .INFO: New Access Token: eyJraWQi*** [] [] [2026-2-10, 14:33] Expiration time:.INFO: Current time: 2026-2-10, 08:33 Estimated expiration time: 2026-2-11, 08:33 [] []
Yes the 2.16.1 release is the primary one with intended changes to help re-establish consistent authentication flows again. We did push those changes to everyone.
Based on what I’m seeing above, you’ve been successfully refreshiing for a good handful of days now, and the admin notification may have been a leftover from around the 6th of the month.
If you want, we can do a test submission to one of your intended forms to see if we get through to being added to the list.
I assume a spot to see a form is in the footer at the end of the page on https://www.bigsystems.com/ ?
omg I just logged in this morning and yep they are gone now. sorry for wasting your time.
No time wasted, we appreciate you sticking with us through this topic.
You must be logged in to reply to this topic.