Unknown Error When Triggering Cron Manually

  • Billy Wilcosky

    (@wilcosky)


    2 weeks, 3 days ago

    I noticed my cron jobs stopped triggering sometime beginning of this month. Today, I disabled all plugins. Using WP Crontrol, after I enabled each plugin, I clicked run now to run a cron event. Each time things worked until I activated this plugin. With this plugin activated, I click run now, and at first WP Crontrol just showed a warning icon. But it did say that the cron was successfully scheduled to run now. Then I manually try running the same cron even again, and get an admin “unknown error” notification. I can follow the same steps, and I get the error each time. Nothing gets logged when I turn on my error log.

    I see this plugin was recently updated.

    Please test wp cron using something like WP Crontrol.

    • This topic was modified 2 weeks, 3 days ago by Billy Wilcosky. Reason: Edited the title of post
Viewing 15 replies - 1 through 15 (of 15 total)
  • akimbokm

    (@akimbokm)

    2 weeks, 3 days ago

    I am having a similar problem. My cron jobs stopped running about a week ago. I tried triggering cron manually and it had no effect. This cron issue dates back to the most recent auto-update for the Litespeed plugin (version 7.8). After disabling the plugin, cron immediately started working. I am running WP 6.9.3, PHP 8.3, and Litespeed 7.8

    Thread Starter Billy Wilcosky

    (@wilcosky)

    2 weeks, 3 days ago

    Thanks for confirming. I’m going to try this but even if that works, I think the last update made wp cron issues worse.

    Thread Starter Billy Wilcosky

    (@wilcosky)

    2 weeks, 3 days ago

    And I can confirm the above change (setting up a real cron) doesn’t work either. Latest version of this plugin breaks WP cron jobs.

    Plugin Support litetim

    (@litetim)

    2 weeks, 3 days ago

    @wilcosky and @akimbokm to start investigating please send a report from a site you are testing.
    Report is created from LSC => Toolbox => Report => click on “Send to Litespeed” and share the ID generated(just the ID).

    Plugin Support litetim

    (@litetim)

    2 weeks, 3 days ago

    There is a known issue that was fixed from 7.8. Can you test the new code and see if this fixes the issue? This can be done from LSC => Toolbox => Beta Test => click on master(branch v7.8.0.1-rc1) and click on Update.
    Also, report IDs will help too 🙂

    Thank you!

    • This reply was modified 2 weeks, 3 days ago by litetim.
    rush_developer

    (@rushcolead)

    2 weeks, 3 days ago

    I am having the exact same issue, cron stuck after automatic Litespeed Cache update and several scheduled posts not published. I did the Beta Test you suggested with the master branch and it caused a critical error across my site.

    Is it something to do with this line in the changelog? :

    Object Cache – Dropped Store Transients option. Transients now always use Object Cache when available

    Plugin Support litetim

    (@litetim)

    2 weeks, 3 days ago

    @rushcolead can you share the error message that occurred?
    Yes, the fix is about that changelog

    • This reply was modified 2 weeks, 3 days ago by litetim.
    • This reply was modified 2 weeks, 3 days ago by litetim. Reason: Revision to make the answer clear
    rush_developer

    (@rushcolead)

    2 weeks, 3 days ago

    11-Mar-2026 16:10:09 UTC] PHP Fatal error: Cannot redeclare wp_cache_init() (previously declared in /home/mysite/public_html/wp-content/plugins/litespeed-cache/src/object.lib.php:42) in /home/mysite/public_html/wp-includes/cache.php on line 21

    I deleted Litespeed plugin folder then reinstalled version 7.8 and I could see that in the Object Cache settings in Litespeed it said:

    Memcached Extension : Enabled
    Redis Extension : Enabled
    Connection Test: Failed

    I turned off Object Cache and then Toolbox > purge all, and that has resolved the issue and Cron is now working.

    • This reply was modified 2 weeks, 3 days ago by rush_developer. Reason: misread the question
    Plugin Support litetim

    (@litetim)

    2 weeks, 3 days ago

    @rushcolead perfect 🙂 Error log would help us fix the update error.

    In 7.8 we changed how transients are saved, they will always be saved to OC. If OC is not correctly setup, transients will not be saved.
    In 7.8.0.1(master branch for now) we added away to auto disable OC when connection is not correctly setup.

    • This reply was modified 2 weeks, 3 days ago by litetim.
    • This reply was modified 2 weeks, 3 days ago by litetim.
    Plugin Support litetim

    (@litetim)

    2 weeks, 3 days ago

    @akimbokm and @wilcosky I made some tests with WPControl and OC turned ON with master branch
    Cron seems to work as expected.

    • This reply was modified 2 weeks, 3 days ago by litetim.
    Plugin Support Hai Zheng⚡

    (@hailite)

    2 weeks, 3 days ago

    @rushcolead Could you provide a report num w/ the issue? Is your setup a network(multisite) WP?

    akimbokm

    (@akimbokm)

    2 weeks, 3 days ago

    I just submitted a report with id ZIZLRPKG

    I am disabling the plugin for now and do not want to try the beta yet; this is a production site and I don’t have a staging site for it.

    Thread Starter Billy Wilcosky

    (@wilcosky)

    2 weeks, 3 days ago

    @litetim Thank you! Yes, the new master version works.

    rush_developer

    (@rushcolead)

    2 weeks, 2 days ago

    @hailite I have submitted now with report number QWSDDJNI. Yes it’s a multisite.

    Plugin Support Hai Zheng⚡

    (@hailite)

    2 weeks, 2 days ago

    @rushcolead Can you give latest master a try? It should have fixed the multisite fatal error.

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

You must be logged in to reply to this topic.

Tags