Constant Contact Forms has experienced issues that may need addressed

  • Resolved Josiah

    (@colewebdev)


    2 months, 3 weeks ago

    Seeing the following 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.

    Log contents:

    [2025-12-30, 12:54] API.INFO: ConstantContact_API::get_lists:420 unauthorized: Unauthorized [] []

    The plugin is “connected”. When I visit the “Disconnect” screen, it shows an active connection to Constant Contact.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Josiah

    (@colewebdev)

    2 months, 3 weeks ago

    Update: Had the client reconnect and the error seems to have gone away (at least for now)

    [2025-12-30, 12:54] API.INFO: ConstantContact_API::get_lists:420 unauthorized: Unauthorized [] []

    New log additions:

    [2026-1-05, 16:05] Error: .INFO: Invalid state or auth code! [] []
    [2026-1-05, 16:05] Error: .INFO: Invalid state or auth code! [] []
    [2026-1-05, 16:05] Error: .INFO: Invalid state or auth code! [] []
    [2026-1-05, 16:05] Refresh Token:.INFO: Old Refresh Token: *** [] []
    [2026-1-05, 16:05] Access Token:.INFO: Old Access Token: *** [] []
    [2026-1-05, 16:05] Refresh Token:.INFO: Refresh token successfully received [] []
    [2026-1-05, 16:05] Refresh Token:.INFO: New Refresh Token: j8V0ecHX* [] [] [2026-1-05, 16:05] Access Token:.INFO: New Access Token: eyJraWQi* [] []
    [2026-1-05, 16:05] Expires in:.INFO: Expiry: 86400 [] []
    [2026-1-05, 16:06] Refresh Token:.INFO: Refresh token triggered [] []
    [2026-1-05, 16:06] Refresh Token:.INFO: Old Refresh Token: j8V0ecHX* [] [] [2026-1-05, 16:06] Access Token:.INFO: Old Access Token: eyJraWQi* [] []
    [2026-1-05, 16:06] Refresh Token:.INFO: Refresh token successfully received [] []
    [2026-1-05, 16:06] Refresh Token:.INFO: New Refresh Token: hK6s6UJP* [] [] [2026-1-05, 16:06] Access Token:.INFO: New Access Token: eyJraWQi* [] []
    [2026-1-05, 16:06] Expires in:.INFO: Expiry: 86400 [] []

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    2 months, 3 weeks ago

    Hi @colewebdev

    We’re still trying to work out potential ways to better detect when token refreshes fail, which is when we get cases like yours where the plugin can no longer self regulate its API tokens, and a human needs to re-authenticate. You did what was needed here to do that.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.