Hmm. Not familiar with this unable to send to backend error as that’s not one provided by our plugin, and I’m not managing to find that message string in WordPress core.
I definitely know we have some checks around WP_CRON being available, and I believe the admin notification should be dismissable, though I could see why it’d potentially not be too.
That said, I also know we have this snippet of code as part of the API integration to try and help make sure access tokens are still getting refreshed:
if ( defined( 'DISABLE_WP_CRON' ) && DISABLE_WP_CRON ) {
if ( $this->access_token_maybe_expired() ) {
$this->refresh_token();
}
}
It just happens to potentially run a bit more frequently because of WP_CRON being disabled.
Ok thank you for letting me know. The plugin does appear to connect but we get constant emails with the following error:
“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.”
Can you visit our Settings > Support tab, and toggle on the debug logs checkbox? This will add in some extra logging and reveal a hidden menu that gives access to the logs. Would love to see if things are actually failing, or if there’s potentially just some excess admin notifications coming through.
We’d be able to better determine if API credentials are actually renewing themselves as needed.
Thanks so much, ok straight away I can see:
[2025-10-08T13:41:47.985764+00:00] API.INFO: ConstantContact_API::get_lists:420 unauthorized: Unauthorized [] []
In the logs…
If you’d prefer to share all the logs privately, they can be sent to wordpresssupport@constantcontact.com and they should make their way to us to further review.
Thank you Michael, have sent the full log.
Confirmed receiving and will review as soon as able and get back to you.
