Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Caitlin Shannon

    (@ckthompson)

    Oh! I just noticed that we needed to reconnect again. I’ve done this. But I also had to reconnect last week. Is there a reason this keeps happening?

    Thread Starter Caitlin Shannon

    (@ckthompson)

    Oh my goodness, I’m sorry, I didn’t realize the logs started with oldest first. Here are some newer ones. We got a notice that a subscription was missed:

    [2026-4-21, 11:14] Expiration time:.INFO: Current time: 2026-4-21, 04:14 Estimated expiration time: 2026-4-22, 04:14 [] []
    [2026-4-21, 21:00] API.INFO: Submitted contact data ["Extra information",[{"first_name___86d40036bc67c631a665bc9940637d30":{"key":"first_name","val":"Daniel"},"last_name___475dd089f4be1ba09db1ab95c87f4248":{"key":"last_name","val":"Michael"},"email___8d9b9760aed7a7e3c5c5b531c77e07d4":{"key":"email","val":"@strawberryhillmusic.com"},"email":"@strawberryhillmusic.com","lists___087addc027674b98a14d15195dabe58f":{"key":"lists","val":""},"list":["536868c6-f99a-11ed-968b-fa163e638ddc"],"anniversary":{"key":"anniversary","val":""}}]] []
    [2026-4-21, 21:35] API.INFO: Submitted contact data ["Extra information",[{"first_name___86d40036bc67c631a665bc9940637d30":{"key":"first_name","val":"Cambria"},"last_name___475dd089f4be1ba09db1ab95c87f4248":{"key":"last_name","val":"Martin"},"email___8d9b9760aed7a7e3c5c5b531c77e07d4":{"key":"email","val":"@gmail.com"},"email":"@gmail.com","lists___087addc027674b98a14d15195dabe58f":{"key":"lists","val":""},"list":["536868c6-f99a-11ed-968b-fa163e638ddc"],"anniversary":{"key":"anniversary","val":""}}]] []
    [2026-4-22, 11:15] Refresh Token:.INFO: Refresh token triggered [] []
    [2026-4-22, 11:15] Error: .INFO: invalid_grant: The refresh token is invalid or expired. [] []
    [2026-4-22, 11:15] Refresh Token:.INFO: Refresh token revoked (invalid_grant). Manual reconnect required. [] []
    [2026-4-22, 11:15] API.INFO: Refresh token attempt failed in get_api_token. [] []
    [2026-4-22, 11:15] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-4-26, 05:14] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-4-27, 05:14] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-4-28, 05:16] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-4-29, 16:49] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-5-01, 02:47] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-5-02, 03:13] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-5-03, 03:31] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-5-04, 06:18] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-5-05, 06:28] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-5-06, 07:18] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-5-07, 08:00] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-5-08, 08:32] API.INFO: ConstantContact_API::get_lists:1114 unauthorized: Unauthorized [] []
    [2026-5-16, 14:24] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-16, 14:47] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-18, 17:18] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-18, 21:42] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-19, 13:53] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-20, 00:48] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-20, 19:14] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-22, 23:55] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-26, 11:47] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-27, 04:04] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    [2026-5-27, 13:39] API.INFO: A failed API attempt was caught and will be retried after reconnection. [] []
    Thread Starter Caitlin Shannon

    (@ckthompson)

    Oh, okay! Yes, I reconnected yesterday morning. So we shouldn’t need to do anything else?

    Thread Starter Caitlin Shannon

    (@ckthompson)

    I’ve cleared the server-level Varnish cache several times and I just installed a caching plugin (after deleting the plugin entirely) and then told it to clear the cache several times and the wheel is still showing up. It shows up for both my client and I, logged in and in private incognito windows. I also tried opening it in a browser (Firefox) that I have never used to view the website and it STILL shows up. Any ideas?

    Thread Starter Caitlin Shannon

    (@ckthompson)

    That appears to have done the trick! Thanks so much 🙂

    I’m seeing a new version (1.0.8) that came out last night, and it doesn’t appear to throw any errors on my site now that I’ve updated. So I think we’re good now!

    Same here, on my client’s site (adventuresofemptynesters.com).

    Thread Starter Caitlin Shannon

    (@ckthompson)

    It actually looks like it may have been a hosting issue! The cURL error DID go away when I deactivated Instagrate Lite, but it came back eventually. Switching hosts appears to have fixed the issue. So for now, I wouldn’t worry about it! I’ll reach out via https://intagrate.io/contact/ if the problem pops up again 🙂 Thanks so much for the reply!

    Thread Starter Caitlin Shannon

    (@ckthompson)

    Hi, Iain! Unfortunately, it occurs as soon as I reactivate Instagrate Lite. When I deactivate, it instantly goes away and the load speed of the backend drastically improves. My client has had this plugin for a while, so I don’t know if recent WordPress updates have caused the issue — but it’s making the admin unsustainably slow (like, 20-30s load times).

    Then entire error that appears in Site Health is as follows:

    1 critical issue
    The REST API encountered an error

    The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.

    The REST API request failed due to an error.
    Error: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed)

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