Cron error detected

In some cases you might the the following notice on your dashboard:

Because your cron has not been triggered more than 24 hours, Burst has stopped using the summary tables, which allow the dashboard to load faster.

This notice can only show up if your site matches the following conditions:

• Your site is a high traffic site: over 200000 hits per month
• The WordPress cron is not triggering

The cron is used to generate summary tables. Not having summary tables is in itself not a problem: Burst will automatically fallback to use the raw data table. If you select a very long range of data, your dashboard might load a bit slower.

If this is not a problem, you’re fine. if you want the plugin to use the summary tables, read on!

How to enable a cron job on your site. 

Please contact your hosting company, and ask them to set up a cron job which triggers yourdomain.com/wp-cron.php every hour at least. For more fine grained cron functionality, you can increase this to every 5 minutes.