How activity feeds are used

Activity feeds are introduced to give our users a better understanding in the way our cron job monitoring algorithm works. It also gives you a clear view of your cron job's activity and performance. The activity feed is calculated ahead of time and is cleared based on pulses from your cron job.

How can I improve the calculation of the cron job's duration?

By default, Cronly calculated the time between the scheduled date and time, and the date and time a pulse was received. This gives you some insights in the time your cron job takes to run, but isn't an exact metric. It's also possible to implement our cron job start endpoint. This gives us the exact moment your cron jobs starts. This can be a few seconds after the exact run schedule.

If you decide to implement the start endpoint, our monitoring algorithm switches to High Resolution Timing. Which is one of the most accurate ways to calculate running times.

What statuses are possible for the activity feed?

• missed A scheduled run didn't receive a pulse in time, but a pulse was received within the delay you've set for your monitor. If this happens a lot, your cron jobs are overlapping and you might want to consider a different schedule.

• failed A scheduled run didn't receive a pulse in time and the delay was reached. We've alerted you.

• ok We've received a pulse in time and cleared the scheduled date.

• planned This date is in the future.

• running The scheduled date is due and we're waiting for a pulse.