• Resolved photocoen

    (@photocoen)


    Heya there,

    I’m running into a strange performance issue. The Site Health is giving me this error:

    A Scheduled Event is late

    The scheduled event, koko_analytics_aggregate_stats, is late to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

    Not sure what this is all about…

    Adventurous greetings, Coen.

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Lap

    (@lapzor)

    Do you have a pretty low traffic site?
    WP Cron is triggered by website visitors, so if you don’t have many visitors yet it can sometimes be behind.

    If you don’t want this to happen, you could setup a free uptime monitor, those will visit your site every 5 minutes to see if it’s online and that will also trigger wp cron.

    https://uptimerobot.com is one example of such service.

    Hope that helps. If you have any questions, please let me know!

    Thread Starter photocoen

    (@photocoen)

    Traffic is not the issue:

    Jul 21, 2020 — Aug 18, 2020
    Stats |Settings
    Total visitors
    10.2K -9%
    1044 less than previous period
    Total pageviews
    16.1K -6%
    959 less than previous period
    Realtime pageviews
    36
    pageviews in the last hour

    I have set the Cron job in cPanel to every 10 minutes

    Plugin Support Lap

    (@lapzor)

    Ok,

    In that case maybe it’s worth installing the Advanced Cron Manager plugin to take a look at your WP corn queue, see if anything is stuck on top of the queue.

    Thread Starter photocoen

    (@photocoen)

    okay I will look into that…

    Actually the message has gone since I was experimenting with the cron job in cPanel.

    Thanks for the tips

    Plugin Author Danny van Kooten

    (@dvankooten)

    Hey @photocoen,

    The notice is probably because your cronjob is only running every 10 minutes, yet ideally Koko Analytics wants to run every minute. If your website does not have thousands of visitors per minute, you can safely ignore the notice and keep on using a 10 minute cronjob interval.

    That said, for a computer 10 minutes is like an eternity and it’s probably more efficient running it every 1 minute instead (which means less jobs to run, so jobs are spread out more evenly).

    I hope that clarifies a little. Good luck!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Site Health error’ is closed to new replies.