• Resolved bonestorm

    (@bonestorm)


    I changed my SALTS which triggered a myriad of issues with Spotlight. I finally got the handshake settled but now the import_batch cron job is evidently failing:

    The scheduled event, spotlight/instagram/import_batch, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

    I haven’t uninstalled/reinstalled the plugin-yet. My resources say that won’t be helpful, but I don’t know. Thanks in advance!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Hendra Setiawan

    (@hendcorp)

    Hi @bonestorm

    Thanks for reaching out and providing a detailed explanation. That helps a lot.

    When WordPress reports that the scheduled event spotlight/instagram/import_batch “failed to run,” it’s unfortunately a bit generic. It simply means WordPress attempted to execute that cron task and it did not complete successfully. It does not automatically tell us why.

    A couple of quick clarifications that will help narrow this down:

    1. When you mentioned that the “handshake settled,” does that mean you reconnected your Instagram account in Spotlight? If you’re unsure, you can do this by navigating to Instagram Feeds → Settings → Accounts, then clicking the Reconnect option from the Actions dropdown on the far right.
    2. Did this cron warning appear right after you clicked Update Posts, or is it happening on its own in the background?

    Once we have the answers to the above, we can guide you more precisely.

    Thread Starter bonestorm

    (@bonestorm)

    The warning appeared right after changing the SALTS…. but I think I got it working. I did an uninstall and reinstall. I even did a command to flush stuff after the uninstall. Even though the Instagram connection config persisted after the reinstall, it does appear to be working. For now, I’ll just monitor. I don’t see any other issues.

    Plugin Support Hendra Setiawan

    (@hendcorp)

    Hi @bonestorm

    Thanks for the update, and I’m glad to hear it appears to be working again. If the feeds are updating and the warning hasn’t returned, everything should be fine.

    Please keep monitoring as planned, and feel free to reply here if you notice anything unusual.

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

You must be logged in to reply to this topic.