Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author webheadcoder

    (@webheadllc)

    Sorry, for some reason I didn’t get notified of this post.

    From the screenshots it looks like the jobs are taking longer than 1 minute to complete. The time of the failed jobs in the email and on the dashboard indicate the last failure was October 11 10:59am or earlier. However, the logs only show as early as 11:06am due to the 3-log limit of the free version.

    While I did want to limit the free version, I didn’t intend for users to be alerted of errors and not be able to see them. I’m currently working on an update to keep the logs with errors around long enough so it can be seen.

    Thank you for letting me know.

    Plugin Author webheadcoder

    (@webheadllc)

    Thank you for your patience. The plugin has been updated to version 1.1 today. Basically all the updates that went into this version are related to this post.

    You should be able to see the error logs now in the WP-Cron Status page. The errors can be seen in the “View Uncompleted…” sections These errors will be shown up to 24 hours after an email is sent.

    You can now keep logs up to 24 hours instead of just 12.

    Previously crons that used the WP_Background_Process would be logged as failed because the hooks tied to that class would either abruptly exit the code or call wp_die(). Both of these would prevent detection of a completed cron job. I believe rocket_preload_cron and rocket_critical_css_generation_cron are from that WP_Background_Process class. So those hooks should no longer show as failing, but will not have an elapsed time.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘always showing failed’ is closed to new replies.