Constant Contact Forms has experienced issues

  • Resolved dtlyme

    (@dtlyme)


    4 months ago

    Here is the DeBugs log:

    [2024-02-07T11:16:21.661216+00:00] API.INFO: ConstantContact_API::get_lists:335 server_error: [] []
    [2024-02-07T12:47:13.810076+00:00] API.INFO: ConstantContact_API::get_lists:335 server_error: [] []
    [2024-02-07T18:57:22.645071+00:00] API.INFO: ConstantContact_API::get_lists:335 server_error: [] []
    [2024-02-08T01:28:25.591134+00:00] API.INFO: ConstantContact_API::get_lists:335 server_error: [] []
    [2024-02-08T02:27:56.324406+00:00] API.INFO: ConstantContact_API::get_lists:335 server_error: [] []
    [2024-03-08T13:55:43.521339+00:00] API.INFO: ConstantContact_API::get_lists:335 server_error: [] []
    [2024-03-08T14:43:20.984525+00:00] API.INFO: ConstantContact_API::get_lists:335 server_error: [] []
    [2024-05-10T14:07:46.554955+00:00] Refresh Token:.INFO: Refresh token triggered [] []
    [2024-05-10T14:07:46.849189+00:00] Refresh Token:.INFO: Old Refresh Token: SkRL9AmZ* [] [] [2024-05-10T14:07:46.849330+00:00] Access Token:.INFO: Old Access Token: eyJraWQi* [] []
    [2024-05-10T14:07:46.852248+00:00] Refresh Token:.INFO: Refresh token successfully received [] []
    [2024-05-10T14:07:46.852355+00:00] Refresh Token:.INFO: New Refresh Token: 0urdNlVI* [] [] [2024-05-10T14:07:46.852428+00:00] Access Token:.INFO: New Access Token: eyJraWQi* [] []
    [2024-05-10T14:07:46.852495+00:00] Expires in:.INFO: Expiry: 86400 [] []

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    4 months ago

    Hi @dtlyme

    Based on the provided logs, there were some issues with tokens last spring, but nothing new beyond that for that log file.

    Are you experiencing any other issues at the moment? Or are submissions coming through still? I can do a test submission if needed.

    Thread Starter dtlyme

    (@dtlyme)

    4 months ago

    oh jeez I am just realizing the date on that. Let me go look at that again!!!

    Thread Starter dtlyme

    (@dtlyme)

    4 months ago

    Ok here is the most recent:

    [2026-2-03, 15:40] Refresh Token:.INFO: Refresh token triggered [] []
    [2026-2-03, 15:40] Refresh Token:.INFO: Old Refresh Token: U1vISzIj* [] [] [2026-2-03, 15:40] Access Token:.INFO: Old Access Token: eyJraWQi* [] []
    [2026-2-03, 15:40] Refresh Token:.INFO: Refresh token successfully received [] []
    [2026-2-03, 15:40] Refresh Token:.INFO: New Refresh Token: 9rO0cEbP* [] [] [2026-2-03, 15:40] Access Token:.INFO: New Access Token: eyJraWQi* [] []
    [2026-2-03, 15:40] Expires in:.INFO: Expiry: 86400 [] []
    [2026-2-04, 14:28] Refresh Token:.INFO: Refresh token triggered [] []
    [2026-2-04, 14:28] Error: .INFO: invalid_grant: The refresh token is invalid or expired. [] []
    [2026-2-04, 14:28] Refresh Token:.INFO: Expired. Refresh attempted at 2026-2-04, 09:28 [] []
    [2026-2-04, 15:23] API.INFO: Refresh token attempt failed in get_api_token. [] []
    [2026-2-04, 15:23] API.INFO: Refresh token attempt failed in get_api_token. [] []
    [2026-2-04, 15:23] API.INFO: ConstantContact_API::get_lists:449 unauthorized: Unauthorized [] []
    [2026-2-06, 15:28] API.INFO: Refresh token attempt failed in get_api_token. [] []
    [2026-2-06, 15:28] API.INFO: Refresh token attempt failed in get_api_token. [] []
    [2026-2-06, 15:28] API.INFO: ConstantContact_API::get_lists:449 unauthorized: Unauthorized [] []
    [2026-2-06, 15:28] API.INFO: Refresh token attempt failed in get_api_token. [] []
    [2026-2-06, 15:28] API.INFO: Refresh token attempt failed in get_api_token. [] []
    [2026-2-06, 15:30] API.INFO: Refresh token attempt failed in get_api_token. [] []
    [2026-2-06, 15:30] API.INFO: Refresh token attempt failed in get_api_token. [] []
    [2026-2-06, 15:32] API.INFO: Refresh token attempt failed in get_api_token. [] []

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    4 months ago

    No worries.

    For timing sake, did you perform the 2.16.0 upgrade this week? or have you had that since before the 3rd of this month?

    Curious if that specific version was working for a time, for refreshing token access, or if it started failing the moment the upgrade was performed. Asking cause we’ve had some issues with that specific release, as reported by others.

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

You must be logged in to reply to this topic.